From owner-freebsd-hackers Tue Mar 28 02:20:13 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA06186 for hackers-outgoing; Tue, 28 Mar 1995 02:20:13 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA06180 for ; Tue, 28 Mar 1995 02:20:02 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id LAA17819 for FreeBSD-hackers@FreeBSD.org; Tue, 28 Mar 1995 11:21:00 +0100 From: Paul Richards Message-Id: <199503281021.LAA17819@isl.cf.ac.uk> Subject: Re: httpd as part of the system. To: FreeBSD-hackers@FreeBSD.org (FreeBSD hackers mailing list) Date: Tue, 28 Mar 1995 11:20:59 +0100 (BST) In-Reply-To: <2819.796380480@freefall.cdrom.com> from "Jordan K. Hubbard" at Mar 28, 95 00:48:00 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1723 Sender: hackers-owner@FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who said > > > I really get scared when people start moving things like ncftp and lynx into > > the /src tree. Who the hell has time to keep everything tracked? Who the > > Well, let's be fair. Things like ncftp moved in because we needed > some sort of default ftp command that the installation framework could > COUNT ON to do unattended ftps. The release framework doesn't have > provisions for dealing with pieces that need to be obtained from ports > or packages, so.. If somebody has a yen to HELP with the install > framework, trust me - we won't argue! :-) I think ncftp will go away at sometime because it's a real pain. Not until we write a replacement though. > > > you needed it or not. Frankly, I think a package-collection feature added > > to the package tool would be cool... then I could specify an uber package > > consisting of: > > Indeed. Now who's going to write the ueberpackage framework? :-) I think the whole idea of system modules and packages needs a re-think. The differentiation between the two is unnecessary. The main difference is that system modules are b-maked and fall seamlessly into the src tree, whereas ports do not. However, the mechanism for loading/unloading modules/packages should be combined so there's one interface to the whole thing and then things will be greatly simplified. There'll still be the arguments about whether things should become an integral part of the system or not... -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff.