Hi, On Mon, 21 Mar 2011 06:36:19 +0100, Julien Valroff <[email protected]> wrote: > > 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.
Indeed, using 1.2.1~ only makes sense when it is absolutely certain that the next version will indeed be 1.2.1! > I think there's no universal answer to the original question, but just > common sense and good use of `dpkg --compare-versions'. That's an excellent summary, thanks. Regards, Stephen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
