On Tue, Aug 18, 2009 at 04:25:37PM -0500, Manoj Srivastava wrote:
>         Given that devscripts,  lintian,  and the dev-ref
>  all advocate  or implement  +nmu\d+, and that debhelper and  cdbs look
>  at the hyphen for determining native vs non-native,  I have tried to do
>  so.  I think the proposed practice is strictly better  than not
>  specifying any conventions, and where possible, Ihave tried to stick to
>  best practices as documented in the dev-ref to base policy on.

>         Having said that, there are a lot of packages that seem to still
>  use versions like m/\-\d+\.\d+$/, so perhaps we should be couching this
>  policy change as a 'recommends', and letting lintian warn about the
>  version number.

I don't agree that this is something that should be recommended.  Changing
the convention for NMU versioning of non-native packages is not necessary
in order to correct the use of confusing version numbers for NMUs of native
packages.  If the dev-ref is recommending +nmuN for non-native packages,
then I think that's a bug in the dev-ref - a common enough problem given the
lack of a public process for dev-ref change reviews.

Recommending use of +nmuN for native packages seems like an appropriate
thing for Policy to standardize, since using hyphens makes the package
versions appear non-native and appending ".N" to the version collides with
ordinary versioning conventions for native packages.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slanga...@ubuntu.com                                     vor...@debian.org

Attachment: signature.asc
Description: Digital signature

Reply via email to