cvs commit: src/gnu/usr.bin Makefile src/lib Makefile src/sbin Makefile src/usr.bin Makefile src/usr.sbin Makefile

[Robert Watson]

On Fri, 29 Aug 2003, M. Warner Losh wrote:

> In message: <Pine.NEB.3.96L.1030829090446.44583A-100000 at fledge.watson.org>
>             Robert Watson <rwatson at FreeBSD.org> writes:
> : I was somewhat hopeful that a further outcome might be that Makefiles are
> : scattered around containing fields like:
> : 
> : COMPONENT=	ACPI
> : COMPONENT=	OPENSSL
> : 
> : so that individual Makefiles would contain positive assertions about what
> : they are, meaning that the Makefile infrastructure could later be tweaked
> : to do installs of only those components...
> 
> I'm not completely sure that marking things to this level would be
> completely useful.  I went down that path at one point, but to create a
> bootable system, you need such an eclectic list of things...  There
> should be a better concept of things.  We have identified a minimal list
> of things to have to boot rc files (I haven't redone this for 5)  and
> then the minimal network utilities. 
> 
> I guess I'm saying that packaging is hard and to do simple things is
> easy, but will lead to a big mess if we aren't careful. 

Well, where we currently sit is that we've identified a set of
semi-optional components -- areas where we've already done some
build/install partitioning.  Let's just slightly enhance the
infrastructure around the existing identifications, and not get too caught
up in identifying new partitioning -- partioning and dependencies are
hard. 

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert at fledge.watson.org      Network Associates Laboratories