On Tue, 26 Jan 1999, RT wrote: > I highly doubt that I'll ever use FORTRAN directly or indirectly. If it's > not used by a vast majority, it should be optional...
So the problem seems to be that 'included in the system' is a problem because the system gets unwieldy in terms of junk a lot of people don't use, but 'included as a port' or 'included as a package' means it might be too detached from the system. There's quite a list of things on this list, including UUCP which the majority do not use. There's also that list of things which almost everyone use except some people who find it inconvenient that it's included, such as sendmail. What might be really nice is to see all user-land files broken out into whatever the new package format will be, in the style of RedHat packages for the base system. At install, needless to say, you have a default install that looks just like today's (it installs the packages that map directly to the current system), but you also have other installs, and the option to flag things in and out of the install, in the style of existing packages, with dependencies, etc. One sad side-effect of this would, of course, be managing the dependencies (both in source and in binary form)and the screwing up of the existing build tree if the build tree was to be restructured to match the packages. But the RedHat arrangement does have appeal: I understand that even / is part of a package :). And I certainly don't have time (and probably not the understanding) to figure out how to make all this work. :) Robert N Watson rob...@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
