[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#881431: debian-policy: Clarify a version number is unique field



Hello Christoph,

On Sat, Nov 11 2017, Christoph Biedl wrote:

> So I'd like to suggest an addition to "3.2. The version of a package",
> for clarification, wording in the simplest form:
>
> | For any package, a version number must never be re-used.
>
> What I'd like to express but I guess is a bit too long:
>
> | Unless bitwise identical, no two files that share the base name and
> | have a version number in it may exist anywhere in the archives,
> | ever.

Slight wrinkle here: epochs are not included in filenames.  So we might
have both foo_1.1.dsc and foo_1.1.dsc where one has version 1:1.1 and
the other has version 2:1.1.

> PS: Aside, I like the new presentation format of the policy document
> as seen in </usr/share/doc/debian-policy/policy-1.html>. Improved
> visual, policy version number at the very beginning, maintainer script
> flowcharts, upgrading checklist included, but no additional and
> dangerous requirements for using the document (i.e. works fine without
> JavaScript). Much appreciated.

Thanks!

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


Reply to: