Re: [Proposal] Simplify upstream version string rule
On Sat, 30 Sep 2006 19:38:40 +0200, Benjamin Mesing <bensmail@gmx.net> said:
> [please CC, I am not subscribed] Hello,
> 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.
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?
We have lived for years with programs and people not having
trouble with the upstream version umber, so what has changed?
I am not in favour of forbidding any future use of colons in
upstream package versions just because some one's aesthetics are
wounded.
manoj
--
The meek will inherit the Earth..... The rest of us will go to the
stars.
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: