On Sun, May 11, 2014 at 8:11 PM, Russ Allbery <r...@debian.org> wrote: > Vincent Cheng <vch...@debian.org> writes: > >> From an user's perspective, if I "apt-get install nvidia-settings" and >> it doesn't bring in a set of proprietary nvidia packages as >> dependencies, then I can justifiably say nvidia-settings is RC-buggy >> because nvidia-settings is broken and useless in such a scenario. Hence >> it must depend on nvidia-driver | nvidia-glx | nvidia-alternative (or >> whatever the correct metapackage is), but that's not possible if >> nvidia-settings were to be moved to main. > >> The only possible solution I can think of is for Andreas to distribute >> nvidia-settings as two separate source packages, e.g. src:libxnvctrl in >> main that builds the shared lib and dev packages, and >> src:nvidia-settings in contrib that builds nvidia-settings. > > I thought source packages in main could provide binary packages in > contrib. Am I just making that up? If not, then the source package and > library could go into main and just the nvidia-settings binary package > into contrib. >
Ah, I didn't think about that, but I suppose you and Michael may be right (I certainly can't find anything in Policy 2.2 that prevents this). Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org