Hi Matthias, I think catering to kernel developers solely is kind of backwards for a desktop operating system meant for novices.
I know that its not that difficult to install build-essential, but the fact that it needs to be, when GCC is installed is not really obvious. Needing to know that GCC is the compiler is OK, but that it doesn't work when installed is wrong. I guess the reason it is called build-essential is that compilation does not work without it, so it must be installed with the compiler. Don't you think it would be considered broken if installing emacs installed only the non X version. The thing is that disk is really cheap these days and nobody would care if the build-essential was installed even for people who need to only build kernel modules. There could be a method for removing the build-essential for the extra finicky, or a separate installation target. I guess you mean by "adding a circular dependency", is that build-essential already depends on GCC. But I don't see what's wrong with that. If having circular dependency is fatal, then there is a problem with dpkg. In any case GCC should depend on build-essential. I think build-essential -> GCC is not as important as GCC -> build-essential. Reason is that nobody, knows about a package named build-essential, while a lot of people would know that GCC is the compiler for Linux. Anyway its your baby, and you can make it as user-unfriendly as you want. regards, -anandsr -- Ubuntu 7.10: build-essentials is not installed with a compiler. https://bugs.launchpad.net/bugs/178329 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
