Russ Allbery wrote:
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 b
Harald Dunkel writes:
> Sorry, I did not have such a deep insight into the procedures how the
> Debian policies are maintained. Filing an ER against Debian Policy
> seemed the right way to me. If the Debian Policy Team doesn't feel
> responsible, or if it does not have the resources to write such
Harald Dunkel 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
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 commo
4 matches
Mail list logo
