[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1088443: debian-policy: Recommend Debian package version format when upstream has no releases



Otto Kekäläinen <otto@debian.org> writes:

>> 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.

FWIW, I used to believe the same but this changed my mind -- gnulib is a
rolling stable package with no releases:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069268#10

I believe versions numbers are for humans; incremental integers, dates
and possibly semantic versioning are useful ideas.  I don't object to a
git commit identifier in a version number, but I also wouldn't want to
enforce it as a general rule.  For gnulib I settled on recording the
full git commit identifier in debian/changelog instead.

/Simon

Attachment: signature.asc
Description: PGP signature


Reply to: