Bug#948275: is Debian POSIX compliant?

If Debian introduces a new feature, changes an API or something like this, breaking POSIX compliance, is this a bug? I grew up with several UNIXes listed on the compliance web page. I never understood why df and others had to work different on some Linux distros. IMHO this set of common basic

Bug#948275: is Debian POSIX compliant?

Package: debian-policy Version: 4.4.1.2 I haven't found it mentioned in the policy manual, so I wonder if Debian is supposed to be POSIX compliant (unless noted otherwise)? IMHO a "it goes without saying" is not sufficient. Is it safe to assume that POSIX code works? Regards Harri

Bug#494472: closed by Manoj Srivastava (Debian polisy is not a HOWTO document)

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

Bug#494472: closed by Manoj Srivastava (Debian polisy is not a HOWTO document)

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

Bug#494472: howto integrate external kernel modules?

Package: debian-policy Version: 3.8.0.1 Severity: wishlist I am missing some guidelines/recommendations in DP about how to integrate external kernel modules, which Makefile variables are/ should be defined when the user builds the kernel module package, what the postinst and postrm scripts should

Re: soversion for shared libraries?

Dear Junichi-san, Sorry to say, but I disagree. Surely compatibility issues should be covered in the Debian Policy manual. Esp. looking at Ubuntu compatibility is (or will become) highly important. If Debian doesn't care about the soversion set by other distros or by upstream, and every package m

soversion for shared libraries?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi folks, Maybe I haven't seen it, but IMHO the Debian policy should be more precise about _which_ soversion to use for shared libraries. Can we use our own soversion, ignoring other Linux distros and the rest of the world? Is upstream always right?