Quoting Joey Hess (jo...@debian.org): Thanks, Joey, for bringing this interesting alternative perspective.
Indeed, when committing these changes, I thought that, because that arch-dependent packages are added to Recommends and not Depend, it would not be a problem. Apparently it is. This is what slightly puzzles me, indeed. Anyway: > Re #697890, if we need iw, d-i should install it on appropriate machines. > netcfg already installs wireless-tools when the interface is wireless. > Not all machines with wifi are laptops, or even desktops, as was noted > several times in that bug. Oh, I didn't think this this was, but, indeed, as we already add wireless-tools through netcfg, I see not reason to not use the same concept to add iw when the (installation) interface is wireless (of course, one might argue "what if the installation interface is wired and the system has wireless"). > > 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. Yes, it was my first reaction : why not deal with that in the D.E. instead of dealing with it in tasksel. The need to be on CD#1 was what drove me to commit. If there are alternative solutions, yes we should consider them.
signature.asc
Description: Digital signature
