Joey Hess wrote:
Raphael Hertzog wrote:The problem is not so much on manually installed package but on initial installation. I'm not sure what would get installed via the laptop task if we made that a Recommends...d-i can't afford to install recommends by default (best way to change that is to make all uses of recommends sane to be installed by default). So the laptop task would need to track and list the recommends. Doing something smarter like only installing given recommends on laptop hardware that can use them would also be an option.
I wouldn't mind having the packages installed in the laptop task if that fixes it. However, the laptop task currently uses the task-fields method, which AFAICT means that the dependent packages should list themselves as being part of the laptop task, something that will take quite some effort if we want to do it. That would also be a dependency inversion, with the dependencies basically saying "I'm a dependency of acpi-support (and I express this by being in the laptop task)". Unfortunately, AFAICT switching away from the task-fields method means explicitly listing *all* of the packages in the laptop task, which is not something we'd want to do either. Is a hybrid task-field/list method possible in tasksel?
Cheers, Bart