der Mouse wrote:
> ClassicBSD
would need to be about 'have to have' functionality,
> not 'nice to have' functionality.
The problem, of course, is, whose
idea of "have to have" controls?
This is an easy problem to solve.
Resist the temptation to bundle
non-OS software with the OS.
That doesn't really solve anything; all it does is shift the debates to
the question of what counts as part of the OS.
I think I'm failing to see the problem, though. What does it matter if a
release comes on one CD or five (or DVD, or tapes, whatever)? Surely the only
issue concerning a lean install is that of what bits you need to install to
get a system up and running - so it doesn't matter if there's a C compiler (or
a database, or whatever) on the install media providing that you don't have to
install it. It's the user's choice.
I'm pretty sure a Slackware Linux system can still be installed using a kernel
and a few bits from the 'A' disk set, for instance, giving a footprint of only
a few MB.
I don't see the bloat as coming from the packages, but from the code itself -
more functionality within individual libraries (which for a particular user
might not be needed), coupled with code that's optimised for quickest time to
production rather than efficiency.