Re: how do deal with versionless mercurial software ?
On 15/10/13 22:32, Benjamin Drung wrote:
> On Fr, 2013-10-04 at 13:40 +0200, Dominik George wrote:
>> Vincent Lefevre <email@example.com> schrieb:
>>> Then, do you mean that VCS hashes are sortable?
>> Of course not. One would have to do something like 0~YYYYMMDDnn
>> +gitXXXX in that rare case.
>> My argument for keeping the VCS hash is to ease identifying the code
>> in the package.
> You could put the VCS hash as text in the changelog entry, e.g. "New
> upstream snapshot (git commit XXXX)." and just use the date as Debian
> version (0~YYYYMMDD or 0.YYYYMMDD). In case you need to release two
> upstream snapshots on the same date, you can append .2 (0~YYYYMMDD.2).
I finally asked to the upstream maintainer if he could add a version string suffix to
his source tarball name: he did, no more tricks and everything is fine now.
Anyway, thanks a lot for all the hints and replies.