On Thu, Mar 24, 2005 at 08:42:56AM -0500, Daniel Burrows wrote: > > Actually, what you said was: > > I believe the culprit here is aptitude, which pulls down Suggests: happily > > trying to be helpful for the end-user (and usually is) but which ends up > > generating an over-bloated system. > > But OK, I believe that you *meant* to say "standard packages". Anyway,
I actually ment "Recommends:" since some Standard packages will pull a lot of -dev stuff through Recommends. Sorry. > aptitude also doesn't pull in standard packages by default, except that the > installer tells it to. So what you're asking for is basically that aptitude > selectively ignore the instructions it's given based on "knowing better". I > hope you see why I really don't want to get into that game :-). Yes, and you are right. > > I will try to work this out by changing how tasksel calls aptitude and see > > if that's possible. If not, I will again ask for a feature that tasksel > > could use to ask for Standard: packages but blacklisting some of them, I'm > > not sure if that's even possible right now. > > I believe tasksel does something like "aptitude install ~pstandard". You > could modify this with something like "aptitude install ~pstandard > blacklisted1_ blacklisted2_ ...". The only real problem would be if you > exceeded the maximum command length, in which case I'd have to implement the > TODO item to read commands from a file/pipe. Well, the current list of packages that should be blacklisted would be the development packages that are of 'Standard' priority, that includes: gdb gcc-3.3 dpkg-dev libc6-dev cpp-3.3 manpages-dev flex g++ linux-kernel-headers bin86 cpp gcc g++-3.3 bison make libstdc++5-3.3-dev I'll try and hack that into tasksel and see what consequences adding that has... Regards Javier
signature.asc
Description: Digital signature
