Resurrect discussion: Mixing 32 and 64 bit distro

[Yaakov (Cygwin/X)]

On Thu, 14 Feb 2013 11:02:47 +0100, Corinna Vinschen wrote:
>> Indeed.  Building packages on behalf of a maintainer only having a 32
> bit system should not be much of a problem.  Also, the build farm for 64
> bit is a good idea, and our dept at Red Hat is inclined to provide it.
> 
> But instead of a farm, it might be even sufficient to provide a simple
> mechanism for maintainers to build their package on a 64 bit machine via
> mail:
> 
> Send your cygport file to cygwin-64-build-package AT redhat DOT com, and
> a dedicated 64 bit Cygwin machine will try to build your package.
> Results of the cygport output via mail reply. On success, packages will
> be uploaded to sourceware automatically.

Email?  Three words: "git update hook" :-)

> > Regardless, a helpful step would be to have per-package git repos on
> > sourceware, like I have currently on cygwin-ports.git.sf.net.  This
> > would open up the package maintenance process and hopefully make it
> > easier for others to help with, or adopt, existing packages.
> 
> Isn't adopting packages already easy enough by just fetching the
> existing source package from sourceware?

I'm thinking more along the lines of collaborative development, history
preservation, redundant backups, all the things that (D)VCS are good
for.


Yaakov