Re: [Proposal] Simplify upstream version string rule (5.6.12)

[Benjamin Mesing <bensmail@gmx.net>]

[please CC, I am not subscribed]

Hello,

> Benjamin Mesing wrote:
>> currently the policy has the following rule for upstream version
>> strings:
>>         The upstream_version may contain only alphanumerics[33] and
>>         the characters . + - : (full stop, plus, hyphen, colon) and
>>         should start with a digit. If there is no debian_revision
>>         then hyphens are not allowed; if there is no epoch then
>>         colons are not allowed.

>> I would suggest to change it to:
>>         The upstream_version may contain only alphanumerics[33] and
>>         the characters . + (full stop, plus) and should start with a
>>         digit.

>> To allow hyphen and colon complicates the definition and I believe
>> has small benefit.  

Manoj Srivastava wrote:
>        Sorry, this is not a good justification for additional
> restriction nor one for a policy change. What is so hard to
> udnerstand  about native debian packages should not have a hyphen,
> but there is no restrictions on upstream hyphjen usage in versions?
> Or that upstream versions could have colons as long as the package
> has an epoch?

Of course progams and humans can deal with that. But IMO simplicity is
always benefitial for one of the most fundamental guidelines for the
Debian project. The section in the policy that explains version
numbering is rather technical and could be significantly simplified
without those exceptions.

But it seems that most people value the possiblity to literally reflect
upstream version strings as far as possible higher than the
simplification of the policy.

Best regards 

Ben