Date: Fri, 29 Aug 2003 09:03:08 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: rwatson@FreeBSD.org Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/gnu/usr.bin Makefile src/lib Makefile src/sbin Makefile src/usr.bin Makefile src/usr.sbin Makefile Message-ID: <20030829.090308.108809143.imp@bsdimp.com> In-Reply-To: <Pine.NEB.3.96L.1030829090446.44583A-100000@fledge.watson.org> References: <200308291035.h7TAZ1Wm008611@repoman.freebsd.org> <Pine.NEB.3.96L.1030829090446.44583A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <Pine.NEB.3.96L.1030829090446.44583A-100000@fledge.watson.org>
Robert Watson <rwatson@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.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030829.090308.108809143.imp>