From owner-freebsd-arch Sun Feb 18 1: 3:41 2001 Delivered-To: freebsd-arch@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 14F4237B401 for ; Sun, 18 Feb 2001 01:03:38 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1I92MW01403; Sun, 18 Feb 2001 02:02:22 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102180902.f1I92MW01403@harmony.village.org> To: Jordan Hubbard Subject: Re: Moving Things [was Re: List of things to move from main tree] Cc: "Daniel C. Sobral" , Mark Murray , arch@FreeBSD.ORG In-reply-to: Your message of "Sun, 18 Feb 2001 00:45:32 PST." <9070.982485932@winston.osd.bsdi.com> References: <9070.982485932@winston.osd.bsdi.com> Date: Sun, 18 Feb 2001 02:02:22 -0700 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan, I'd like to point out that making FreeBSD more modular doesn't necessarily mean that we have to change the policy we have hard coded into the Makefiles. We can and do subset things more easily than that. NetBSD builds everything during make build, but has a better layering of system components than FreeBSD, for example. I'm not saying thta it is good or bad. There are pros and cons to both ways. I have a kludge script that just install the minimal (for a suitible definition of minimal) set of files on a target system. I doubt they rise to the level that they could be used for packageNG, but stranger things have happened :-) You do make an excellent point that we do have this policy hard coded into the make files. We have limited support for subsetting in the Makefiles. We can support one set of subsetting for the source upgrades and one class for the binary folks. This may or may not be desirable from a support point of view, but it is what we already do now. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message