Harald Dunkel <harald.dun...@t-online.de> writes: > I am not asking for a howto, but for a packaging policy for kernel > source modules. Similar to the Emacs, Java, Perl and Python policies to > be found on http://www.debian.org/devel/. > > AFAICS there are >50 packages depending upon module-assistant, not > looking at the kernel-package package. Some common guidelines for the > Makefile called by m-a or kernel-package would be helpful, e.g. how to > make sure that a kernel module can be built "cross-version", etc.
I agree that this would be useful but I'm not sure the bug queue for debian-policy is the place to track it. Realistically, the Debian Policy team is unlikely to write such a document from scratch, so having the bug open against Policy doesn't reach someone who's going to be able to do something about it. Usually the way that sub-policies are developed is that the relevant team writes the initial policy document and then opens a bug against debian-policy for review and incorporation. In this case, either module-assistant or kernel-package is probably the right place to write and develop the initial sub-policy, since those are the tools who are attempting to agree on a set of conventions for debian/rules, with input from the kernel team. I'm afraid that if the bug is left open against Policy, it will just linger here. I think you'd have a better chance at having this resolved with a bug open against module-assistant or kernel-package. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
