On Wed, 27 Nov 2024 13:11:14 -0800 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
<o...@debian.org> wrote:
I would like to suggest the Debian Policy to recommend a specific
Debian package version string scheme in cases where upstream has no
releases, but they do have git commit ids to refer to:
***
In case your upstream does not use version numbers, the Debian package
version will look like this: 0.0~git20130606.b00ec39-1
Would it be possible for Policy/devref to recommend a version format for
snapshots in general, and not only for "no releases" upstreams?
Something like:
In case you are packaging a snapshot or your upstream does not use
version numbers, the Debian package version will look like this:
<upstream-ver><snapshot-id>-1
where <upstream-ver> is:
* `<last-upstream-ver>+` if the version number of the upcoming upstream
release is not yet known;
* `<next-upstream-ver>~` if the version number of the upcoming upstream
release is already known;
* `0~` if this upstream has not done a release yet.
and <snapshot-id> is:
<git|svn|hg><yyyymmdd>.<last-commit-hash>
PS: I wouldn't mind having the commit hash in the version number, but in
that case it should be in a format (mostly) compatible with `git show`,
i.e. the commit hash should be prefixed by `-g`.
Regards,
--
Gioele Barabucci
