Sam Hartman <hartm...@debian.org> writes:
>>>>>> "Russ" == Russ Allbery <r...@debian.org> writes:
> Russ> Ian Jackson <ijack...@chiark.greenend.org.uk> writes:
> >> Secondly, there doesn't appear to be any support in policy for
> >> this restriction.
> Russ> Policy definitely supports this restriction, as Guillem
> Russ> pointed out. I want to echo that analysis as one of the
> Russ> people to have touched that portion of the Policy document.
> Citation requested.
> I looked for this today and couldn't find it.
Policy lacks a section that clearly defines native and non-native
packages, which is a long-standing bug in Policy. Currently, that
information is in Policy 5.6.12, which is an inobvious place for it, and
worse, is hidden in the definition of the debian_revision component.
However, the intent is to define native vs. non-native by the version
number format used:
This part of the version number specifies the version of the Debian
package based on the upstream version. It may contain only
alphanumerics and the characters + . ~ (plus, full stop, tilde) and is
compared in the same way as the upstream_version is.
It is optional; if it isn't present then the upstream_version may not
contain a hyphen. This format represents the case where a piece of
software was written specifically to be a Debian package, where the
Debian package source must always be identical to the pristine source
and therefore no revision indication is required.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/877g99qkyx....@windlord.stanford.edu
