On 09/10/2013 01:33 PM, Jan Engelhardt wrote:
On Tuesday 2013-09-10 13:22, Sascha Peilicke wrote:
I'd like to gather some input on versioning schemes used for packaging SCM snapshots. [...] Here's a small list of flavors that I've come across or used myself.[...] TL;DR: My recommendation would be to (at least loosely) follow pattern 5) versioning.
Pattern 5 "X+git.1363873583.8dfab15" is terribly long, and hashes are useless in many situations, either because history is practically linear (like systemd's git) or because you are only ever following master.
In these cases I fully agree. But we also have packages that come from different (stable) branches. Once you change those in Factory, you probably want to have the commit hash again. Although you could probably infer the commit from it's checking time (since it's rather unlikely that 2 commits collide), it is much more obvious to have the commit hash available. The point is to use sth. as unique as possible, sth. like "X+git20130101" could still mean 10-20 commits depending on upstream activity. Lastly, "terribly long" is a matter of taste. But if your package ends up on Joliet FS formatted media it may be an issue indeed :-)
TL;DR: http://en.opensuse.org/openSUSE:Package_naming_guidelines#Handling_special_v... .
Awesome, to be honest I didn't knew this paragraph existed. -- Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)