Joey, am Thu, Mar 07, 2013 at 11:47:17AM -0400 hast du folgendes geschrieben: > Also, if we are going to depend on something linux-specific in a task, > we could | depend on the freebsd equivilant too, and that should work > with the task being arch all. If there is not a freebsd equivilant, we > could | depend on something that documents how to do it the freebsd way. :P > However, we mostly don't depend on things in tasks; we Recommend them. > And recommends don't care if it's not available on some architecture. if we still had type-handling… > Re #697868, I would much rather leave it to the maintainers of desktop > environments (and/or Tech Ctte :P) to ensure that they have eg, > necessary network-manager dependencies on appropriate architectures, > rather than making tasksel need to track that. Reading that bug, the > only reason task-gnome is depending on network-manager is to ensure it gets > on CD#1. There are other ways to do that, particularly debian-cd's > generate_di+k_list is appropriate since netcfg arranges for > network-manager to be installed. netcfg does not at all arrange for network-manager to be installed. It just deals with it if it finds it post-install. Hence the decision to install it still needs to be made properly by another bit of debian-installer. ;-) Kind regards Philipp Kern
Attachment:
signature.asc
Description: Digital signature