On Wed, Nov 27, 2024 at 01:11:14PM -0800, Otto Kekäläinen wrote:
> 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 refe
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 pac
> Please recommend only putting this information into the changelog entry.
> It has no place in the version value.
Sorry, I don't understand, can you elaborate?
In the case of say for example canid 0.0~git20180613.007c9af-2, which
part of this version string do you think does not belong there and
On Wed, Nov 27, 2024 at 05:07:16PM -0800, Otto Kekäläinen wrote:
> > Please recommend only putting this information into the changelog entry.
> > It has no place in the version value.
>
> Sorry, I don't understand, can you elaborate?
>
> In the case of say for example canid 0.0~git20180613.007c9a
> The commit hash. 007c9af.
OK, thanks.
I disagree here - to me the git commit hash is the single most
important identifier for the software version if there are no actual
releases.
5 matches
Mail list logo
