On Wed, 1 Oct 2003, Vincent Danen wrote:

> On Wed Oct 01, 2003 at 11:11:28PM +0200, Luca Berra wrote:
> 
> > I don't believe there is anyone enjoying having to mantain 4 different
> > packages of the same software when one would suffice.
> 
> Probably not.  But if you, as a contributor, have a cooker machine and
> compile on cooker, how can you possibly know if your package, despite having
> conditional build macros, will work with an older distrib if you don't take
> the time to build and test on that old platform?  So you *do* need to
> maintain it in such a manner otherwise you're just pumping out stuff that
> pretends to work on old distribs and you really don't have a clue if it does
> or not.

But, the point is that if people are interested in maintaining their 
packages for rebuild on older releases, then it may be possible to make 
this easier by having automated rebuilds on stable releases.

I don't know if I can offer it, but we have a 150-machine (90 dedicated, 
60 dual-boot) lab running Mandrake 9.1 somewhere here at the university, 
and we have a cooker mirror (that is usually not too far behind). It may 
be feasible (depending on how much time I have available) to set up some 
chroots on a machine on this network and use some or many of these for 
automatic rebuilds. We wouldn't be able to host the binaries, but we could 
probably host build output (ie slbd for stable releases).

Regards,
Buchan

-- 
|----------------Registered Linux User #182071-----------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x121
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
*****************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
*****************************************************************

Reply via email to