build-essential

Jeff Waugh jdub at perkypants.org
Fri Sep 3 21:53:37 CDT 2004


<quote who="Matt Zimmerman">

> I think I've made the case in favour of a compiler fairly clear, but I
> don't understand your argument against it.

We don't put music tagging software in the desktop, claim that 'many' users
will use it, and those who don't use it, won't notice it. We draw a line.
The same goes with build-essential. It is not true that 'many' users in our
intended audience will use a compiler. We can claim it, but it's not true.

So, the first part of my argument against it is that it's inappropriate for
the DesktopSeed to begin with. Our intention with the DesktopSeed is to hit
a sweet spot of commonality among our users, along with minimal install and
on-CD size. build-essential just doesn't stack up - it's important for you
and me, but not for the vast majority of our intended audience.

Secondly, what we put on the Desktop CD - and more importantly, what we
install by default - is a commitment. It's very hard to take something out
once you've put it in. Suppose we include a whole raft of drivers and apps
on the Ubuntu 5.4 CD, and realise that we have too much for the disk. What
do we do? First against the wall is the ShipSeed, but what happens after
that? Someone comes up with the bright idea that our desktop users don't
care about compilers, so build-essential is removed. What happens when you
do a CD-only upgrade?

So while I was happy enough to put build-essential on the ShipSeed, I would
not be at all happy to see it in the DesktopSeed. That selection of packages
has a very specific goal, and build-essential does not fit. But it *will* be
easy to find, install and use - ShipSeed is a great compromise.

- Jeff

-- 
What's all that about?                           http://www.no-name-yet.com/
 
                      Hunch, n.: U.S. Foreign Policy.




More information about the sounder mailing list