From what I read in this bug report, it suggest *two* things: - include important packages in the standard task - make it possible to unselect them Joey clearly answered "no" to the second question, with the basic argument that a package one would want eventually to drop from important is probably not belonging to important. I buy that. I haven't seen an answer to the *first* question, so I'll make mine. The purpose of putting a package in "standard" is.....exactly having it installed by default on default installs. So, merging important into standard just makes the distinction between standard and important pointless. I'm *very* tempted to mark this bug as "wontfix". I'd rather buy the idea of having an "important" task, then maybe even other priorities but maybe extra. --
Attachment:
signature.asc
Description: Digital signature