On 09/10/2013 01:50 PM, Dominique Leuenberger a.k.a. Dimstar wrote:
Quoting Sascha Peilicke <speilicke@suse.com>:
So if you have to package a (random) SCM snapshot, you want to make sure that it's obvious which commit you picked, so that others can confirm and eventually repeat the build. Here's a small list of flavors that I've come across or used myself. Please not that I replaced the stable (upstream) version with X, since that's not the part I'm interested here. Also, the word "git" can be replaced by whatever SCM at hand:
1) X+git 2) X_20041122git 3) X+git20111213 4) X.a258.g003e7e3 5) X+git.1363873583.8dfab15
They have their merits and disadvantages of course. I'd not go as far as making the format a requirement for Factory checkins.
Sure, as mentioned somewhere I for now look at some generic recommendations / best practices.
There are short-living packages and longer-living ones; a package 'always' depending on git snapshots probably wants to express this in the version number; a package doing this 'temporarily' to overcome an obstacle might be fine with any other, shorter, for and only specify the exact commit / branch in the .changes file.
But even then, correctness won't hurt. Even if the git snapshot is temporarily, people want to know which commit was picked. Format 1) doesn't seem to provide this info. -- Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)