On Fri, 25 May 2001, David Brownlee wrote:

> 	One way to reduce the problem of binary packages on ftp.netbsd.org
> 	built against different DEPENDS would be for developers to
> 	perform bulk builds and upload the entire set to ftp.netbsd.org,
> 	delete any existing packages for that arch/osrev, then move the
> 	new set into place.

The problem with that is: 1) It's never going to happen for m68k,
pmax, or vax -- our best candidates for binary packages, in fact, and
2) in order to _use_ those packages, you practically have to throw
away your CD, and blow away all your existing packages to upgrade
anything. What we should be doing, instead, is building to a
consistent baseline. Then, if do a "make package" in news/knews, and
upload all the packages produced, it should work as well for anyone
else as it does for me. The fly in the ointment is when we make
changes to dependencies without bumping the version numbers, so that
you have _completely_ _different_ packages with the same version
number floating around.


Frederick