Re: Git Package Versioning

[Julien Valroff <julien@debian.org>]

Hi,

Le dimanche 20 mars 2011 à 23:16:47 (+0100 CET), Stephen Kitt a écrit :
> On Sun, 20 Mar 2011 22:25:38 +0100, Joachim Wiedorn <ad_debian@joonet.de>
> wrote:
> In this example, the Debian package version could be either
> 1.2.0+gitYYYYMMDD.<githash>-1, which could be read as "everything in the
> 1.2.0 release plus all changes since, up to git hash <...> on YYYYMMDD",

It is indeed what I meant.

> or 1.2.1~gitYYYYMMDD.<githash>-1, which could be read as "the 1.2.1 release
> currently being prepared, as of git hash <...> on YYYYMMDD".

Though it is perfectly correct, I try and avoid using this scheme: what
happens if upstream releases eg. 1.2.1 Beta1 which I would normally version
as 1.2.1~b1?

Even if contact with upstream are good, the may change their mind. Take
Firefox 4 which should have been released after the 1st RC… before they
decide to release a 2nd RC.

I think there's no universal answer to the original question, but just
common sense and good use of `dpkg --compare-versions'.

Cheers,
Julien

-- 
  .''`.   Julien Valroff ~ <julien@kirya.net> ~ <julien@debian.org>    
 : :'  :  Debian Developer & Free software contributor
 `. `'`   http://www.kirya.net/
   `-     4096R/ E1D8 5796 8214 4687 E416  948C 859F EF67 258E 26B1