On Aug 23, Steve Langasek <vorlon@debian.org> wrote: > I think the use case is users who are being control freaks about the set of > packages on their systems. If the set of packages being pulled in as > recommends is *wrong* (they don't fit the Policy definition of Recommends), > bugs should be filed against those packages and be fixed. If the set of > packages is *right*, then there's no good reason to give users a big "ignore > Policy" button at install time. Wrong. My experience as somebody who designed and oversees the installation procedure of "dedicated servers" for a largish hoster showed that not installing Recommends by default saves time and disk space and never caused any issues nor complaints from customers. Indeed this is the first thing our customization script does, so I would appreciate a preseedable configuration knob for this. -- ciao, Marco
Attachment:
signature.asc
Description: Digital signature