From owner-freebsd-hackers Mon Mar 8 2:18: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay02.indigo.ie (relay02.indigo.ie [194.125.133.226]) by hub.freebsd.org (Postfix) with SMTP id DD7D614D8B for ; Mon, 8 Mar 1999 02:17:59 -0800 (PST) (envelope-from nsmart@kira.team400.ie) Received: (qmail 6577 messnum 46530 invoked from network[194.125.134.175/ts02-045.dublin.indigo.ie]); 8 Mar 1999 10:17:40 -0000 Received: from ts02-045.dublin.indigo.ie (HELO kira.team400.ie) (194.125.134.175) by relay02.indigo.ie (qp 6577) with SMTP; 8 Mar 1999 10:17:40 -0000 Message-ID: <36E3A450.2ABBFD0E@kira.team400.ie> Date: Mon, 08 Mar 1999 10:20:00 +0000 From: Niall Smart Organization: Trinity Commerce X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: alk@pobox.com Cc: robert@kudra.com, freebsd-hackers@freebsd.org Subject: Re: base64 References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> <19990306095927.B53145@kudra.com> <14049.29637.311448.247778@avalon.east> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The base system has expanded. DHCP is one recent example. > In the modern world, a system without DHCP is much less generally > useful than one with DHCP. MIME should be another functional > adaptation to the modern environment. Uu-coding can go. (Well, > not yet, but before I die.) > > : Thats why we have the ports tree. If we switched to > : elm for instance, that would be a wasted megabye of disk for me, and > : many other people. Can you say 'Creeping Featureism?' > > Like DHCP. Or C++. Creeping Featurism? I don't think so. > But it would be better to be able to trivially configure a system > without DHCP, or C++, or MIME, I agree. What about the maintanence cost of importing DHCP and a decent C++ compiler into the base tree? There is no point of integrating them without a maintainer who keeps the package in sync with the "vendor sources" in a reasonably timely manner.  IMHO the ports provide the best compromise to cater for per-site customisation without the hassle of maintanence and "lively discussions" over what constitutes a base system. Thats not to say the definition isn't up for debate, but when in doubt "make -f /usr/ports/net/isc-dhcp/Makefile all install" seems best to me. Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message