Harald Dunkel writes:
> If Debian introduces a new feature, changes an API or something like
> this, breaking POSIX compliance, is this a bug?
Maybe? For the most part, it would be an upstream bug, and Debian would
likely follow whatever upstream decided to do. It's not a Debian Policy
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
Harald Dunkel writes:
> 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?
Simon provided the practical
On Mon, 06 Jan 2020 at 12:12:23 +0100, Harald Dunkel wrote:
> I haven't found it mentioned in the policy manual, so I wonder if
> Debian is supposed to be POSIX compliant (unless noted otherwise)?
I suspect what we aim for is "approximately POSIX". Neither the
Linux kernel nor the various
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
5 matches
Mail list logo
