Le jeudi 07 octobre 2010 à 13:57 +0100, Andrew Wafaa a écrit : > On Thu, 2010-10-07 at 13:43 +0100, Ross Burton wrote: > > Is there a best-practise for versioning a git snapshot? > > > > At the moment I'm working towards something like: > > > > [new release number]~[commit count].g[commit hash abbrev] > > > > (inspired by git-describe HEAD) > > > > So if we'd packaged 0.1, then a git snap would be 0.2~42.g123456. > > > > Ross > > _______________________________________________ > > MeeGo-packaging mailing list > > [email protected] > > http://lists.meego.com/listinfo/meego-packaging > > I'm no expert but... > > Using your example, I would recommend you don't use the full new version > number as it will conflict with the actual final release. > > So using your example I would say use: > > 0.1.99_42.g123456 > > Or use the date in there somewhere. > > Also something to keep in mind is that when packaging there are certain > charachters in file names that can cause issues, I forget exactly what > they all are, but I'm sure ~ is one of them.
Well, on openSUSE, ~ is not accepted as a valid version number :( -- Frederic Crozat <[email protected]> Novell _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
