build-essential

Steve Alexander steve at canonical.com
Sat Sep 4 12:17:48 CDT 2004


> I think I have provided at least two "why" arguments:
> 
> Why for me and other developer types: I will use it
> Why for our current users: They have asked for it

I fall into both of these categories of user.  I'll add that I don't 
usually program in C.  I'm with Jeff.  I'd rather not have it in Desktop.

I do use gcc as part of my work if I need to compile Python with various 
debugging options, or I'm developing Python C extension code, or fixing 
bugs in Python itself.

If I need to install gcc on a system that has a packaging system that 
installs binaries, I feel I have passed some sort of watershed.  I have 
moved from "there's a team of people responsible for making sure my 
machine isn't screwed up by what I install and uninstll" to "I'm on my 
own now".

If I install gcc for the Python development tasks I mentioned above, I'd 
still be careful about compiling stuff and installing it when I should 
be getting / making a deb.

I welcome actively choosing to install a set of development tools.

-- 
Steve Alexander




More information about the sounder mailing list