From owner-cvs-all@FreeBSD.ORG Fri Aug 29 08:14:34 2003 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7D5816A4BF; Fri, 29 Aug 2003 08:14:33 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAC6043FEA; Fri, 29 Aug 2003 08:14:32 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h7TFDurO045911; Fri, 29 Aug 2003 11:13:56 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h7TFDuej045908; Fri, 29 Aug 2003 11:13:56 -0400 (EDT) Date: Fri, 29 Aug 2003 11:13:56 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "M. Warner Losh" In-Reply-To: <20030829.090308.108809143.imp@bsdimp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: phk@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 X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Aug 2003 15:14:34 -0000 On Fri, 29 Aug 2003, M. Warner Losh wrote: > In message: > Robert Watson 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@fledge.watson.org Network Associates Laboratories