[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Naming (Re: Unified packages. )



 * From: "Dan Langille" <dan@langille.org>

 * The FreeBSD Project has a cluster of 12 (from memory) boxes that 
 * does this.  It's not a small thing to achieve.  They were in the back room 
 * at Walnut Creek when I was there in October 1999.

9, with 1 server and 8 clients.  The cluster is currently down as most
of FreeBSD.org has moved from Walnut Creek to Yahoo, but we will have
a new cluster running soon.  There is also going to be another one
build in Walnut Creek for alpha packages.

One thing I have put a lot of my time in the past couple of years is
this parallel package build system.  I'm trying to build a system
which will just build as many packages as it can, automatically, and
also produces a set of error logs for people to check periodically.
(You can see the error logs at "http://bento.FreeBSD.org/errorlogs";.)

Basically each package is built in its own chroot directory with an
empty ${LOCALBASE} and ${X11BASE}.  Dependencies are usually installed
from packages.  The "make parallel" target in ports/Makefile will
generate a Makefile suitable for this purpose from ports/INDEX.

The benefit of this transcends automation of package creation.  One is
that it won't pick up transient dependencies.  For instance, if a
certain port has a configure script that detects the presense of
libttf and builds in freetype support, and the port Makefile doesn't
list freetype as a dependency, then we will end up with a package that
doesn't have a @pkgdep freetype line but with a binary linked against
libttf.  Those kind of things won't happen.

If you guys are going for automated package creation, I can help you
put together something like this.  If we can get enough sponsors to do
this for all architectures for all operating systems, that would be
majorly cool.  (Ok, maybe not, but at least the major architectures.)

Satoshi

To unsubscribe: send mail to <majordomo@unixathome.org>
with "unsubscribe bsdports" in the body of the message