On Mon, Oct 20, 2003 at 12:13:22PM +0200, Goswin von Brederlow wrote: > > b) The package is uploaded from real-world environments. Sometimes it > > breaks; when this happens the bug is noticed and corrected, so that > > the package always builds the same way. > > Why would it ever be noticed? That only happens if someone manually > rebuilds the package and notices a difference. Something like being > linked against different versions of libc or even different versions > of libpng might go unnoticed for a long time. If you are arguing that such issues will not be noticed, then you have just defeated your own argument. Your argument has been founded upon the notion that packages built on real-world systems might be broken. You are now saying that nobody will notice - in which case it doesn't matter at all, and the status quo should remain. > > I say that (b) is vastly superior to (a). The tradeoff is temporary > > bugs in sid versus unnoticed bugs in a release. We'll never trap all > > the bugs, but going out of your way to _not look_ cannot be a good > > idea. > > You say that in case B bugs will be noticed, which implies people are > recompiling the packages in their own environments. But then bugs > would just as well be noticed in case A. > > So far the best suggestion for this problem I have heart was to allow > (require) binary uploads but to hold them back and autobuild > everything for all archs. Only binaries allowed into archive are > autobuilders and binary-only uploads (to allow fixing autobuilder lags > or problems). It is evident from these two paragraphs that you did not read my mail and understand it. I have already given reasons for why they are wrong, albeit not attached to the same examples. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -><- |
Attachment:
signature.asc
Description: Digital signature