From owner-freebsd-arch Tue Feb 27 18:13:30 2001 Delivered-To: freebsd-arch@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id A736937B71A for ; Tue, 27 Feb 2001 18:12:29 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.2/8.11.2) with ESMTP id f1S0gq454788; Wed, 28 Feb 2001 00:44:07 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.2/8.11.2) with ESMTP id f1RI1oF00966; Tue, 27 Feb 2001 18:01:50 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200102271801.f1RI1oF00966@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Mark Murray Cc: arch@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: FreeBSD sources from 20000' In-Reply-To: Message from Mark Murray of "Tue, 27 Feb 2001 13:36:49 +0200." <200102271136.f1RBa4R12865@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Feb 2001 18:01:50 +0000 From: Brian Somers Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > REMINDER REMINDER - The whole point of this exercise is NOT to > remove ANYTHING from FreeBSD. Effectively, FreeBSD will become a > grow-only system with the configuration and installation policies > placed in the hands of the owners or sysadmins. By "grow-only", I > do not mean we cannot throw out the trash; it just means that > arguments such as "please don't remove UUCP" or "please remove the > r-utils" are largely irrelevant. [.....] > OK. End of this thought-dump. Who's coming to play? IMHO this is quite an interesting idea - kind of like what Solaris does with it's packages only better. I don't think it'll work though :-) At the moment FreeBSD consists of the base system (we maintain two) and then a bunch of ``other things'' on top. Originally, they were all pretty much distinct/separate, although lately the ports have become quite complicated dependency-wise, and the doc & www trees have a lot of ports dependencies. What you're proposing is way too granular, and the whole dependency tree would be horrific. I believe that a better approach (which isn't radically different to what you're suggesting) would be to make a ``set'' mechanism for the ports - probably just a series of super-ports like docproj or kde. Then we can start pulling things like ``everything in contrib'' out into the ports hierarchy and making super-ports/sets out of them where this makes sense, and progress to system utilities that aren't vital in running a machine. I think the big problem with all of this however is that there's no easy way to keep the ports up-to-date. I know that work is underway here, but until I have a tool that will go into /var/db/pkg and to a ``make buildpackages'' so that I can subsequently ``make installpackages'', I'd be loath to move anything from contrib to ports. > M > -- > Mark Murray > Warning: this .sig is umop ap!sdn -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message