On Wed, 27 Nov 2024 at 13:11:14 -0800, Otto Kekäläinen wrote:
> In case your upstream does not use version numbers, the Debian package
> version will look like this: 0.0~git20130606.b00ec39-1
Is there a reason to use 0.0 here in preference to just 0?
(For example see src:darkplaces, src:openjk)
> * The second part is the version control system, e.g. git, hg, svn.
This can go wrong if an upstream switches from svn or hg to git (or
hypothetically, from git to bzr or fossil or something else earlier in
the alphabet). ioquake3 had a problem like this already: ioquake3 did have
releases in the past (but hasn't had a formal release for a long time, not
even to fix security vulnerabilities), so we're using snapshot versions
starting with 1.36+ instead of 0~, but otherwise it's the same pattern.
In ioquake3, versions like 1.36+svnYYYYMMDD were superseded by what would
have been 1.36+gitYYYYMMDD if it hadn't broken the sorting order. I worked
around this by using 1.36+uYYYYMMDD (u for "upstream git"); another
possibility would have been 1.36+vcsYYYYMMDD.
smcv
