On Tue, 10 Sep 2013 18:06:53 +0200 (CEST), Jan Engelhardt <jengelh@inai.de> said:
On Tuesday 2013-09-10 16:24, Togan Muftuoglu wrote:
For example I maintain nightly builds for darktable for a long time and this is what I use
dt_ver=$(git describe --tags HEAD | sed 's,^release-,,;s,-,_,;s,-,_,;') which results
1.3_929_g6202a15 and the respective field in the spec is Version: %{dt_ver}_git
Interesting case - that can blow up when darktable releases a hypothetical "1.3.1". That is because 1.3.1_1024 < 1.3_929
No it won't since darktable follows a odd/even release number version scheme so currently darktable stable is 1.2.2 and major release will tagged 1.4 and development as 1.5 tagged in the future. Any interim release is going to be 1.2.x
Like http://en.opensuse.org/openSUSE:Package_naming_guidelines suggests, the SCM identifier ("git") should be *before* the SCM ids. IOW, Version: 1.3_git929_g6202a15
Point taken -- Life is endless possibilities -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org