Package: debian-policy
Found: 4.7.0.1

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

* The 0.0 in the beginning is used to allow upstream to adopt version
numbers at any point in time and also to make it clear that no
traditional version number is used for this package.
* The second part is the version control system, e.g. git, hg, svn.
* Afterwards, a date follows in the format YYYYMMDD.
* After the dot, the version control system revision follows, to make
it clear which commit was packaged, as many repositories have multiple
commits on a given day.
* The last part after the dash is the Debian version number.

In case you make more than one snapshot per day, you can append a
snapshot number after the date, e.g. 0.0~git20130606.2.b00ec39-1. This
should rarely be necessary.
***

The text above is from https://go-team.pages.debian.net/packaging.html
but I see also packages outside Go team adhering to this scheme
already.

± grep --only-matching -P '/.*0.0~git.*.deb' Packages | head
/main/a/arpys/python3-arpys_1.0.0~git20230217101414.07b63b3-2_amd64.deb
/main/a/asmjit/libasmjit-dev_0.0~git20231115.1da9e4d-1+b1_amd64.deb
/main/c/c-vtapi/libcvtapi-dev_0.0~git20230329.226eda8-1.1+b2_amd64.deb
/main/c/c-vtapi/libcvtapi1t64_0.0~git20230329.226eda8-1.1+b2_amd64.deb
/main/c/canid/canid_0.0~git20180613.007c9af-2+b28_amd64.deb
/main/c/cht.sh/cht.sh_0.0~git20220418.571377f-2_all.deb
/main/c/cisco7crack/cisco7crack_0.0~git20121221.f1c21dd-3_amd64.deb
/main/c/cl-fiasco/cl-fiasco_0.0~git20200514.bb47d2f-3_all.deb
/main/c/cpuinfo/cpuinfo_0.0~git20240830.fa1c679-5_amd64.deb
/main/c/cpuinfo/libcpuinfo-dev_0.0~git20240830.fa1c679-5_amd64.deb


I am happy to submit an exact patch for the policy to write the final
version of the text in the correct place, assuming I see some general
support for having this included as replies here.

Reply via email to