On Thu Oct 02, 2003 at 03:32:46PM +0200, Guillaume Rousse 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.
> >
> > Yes, but don't you understand that automatic rebuilds is not enough?  It
> > needs to be *tested* first.
> I didn't pretend it was enough, just that getting stable versions for free, 
> without any additional human resources need, would be a gain over current 
> situation.
> 
> It would not bring an updated version of stable distribution for sure, but at 
> least provide packages with far better chance of working on stable version 
> that cooker packages. 
> 
> And nothing prevent packagers from testing on stable, as well as they are 
> testing on cooker.

Right, and this is the part about Club packaging that makes sense.  It goes
into a testing repository first and people try it out and vote on it,
understanding that it's in testing.  Once enough people have tested it and
it's ok, it goes into Club "stable".

My problem is with just pumping out rebuilt stuff, without testing, and
throwing them into a "stable contribs" repository.  If it hasn't been tested
by a person, it doesn't belong in any kind of stable repository.

It isn't cooker, after all.  This is people's production machines.

-- 
MandrakeSoft Security; http://www.mandrakesecure.net/
Online Security Resource Book; http://linsec.ca/
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD}

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to