Am Mittwoch, 15. Februar 2012, 16:33:46 schrieb Greg Freemyer:
All,
I've just been ignoring the release variable in my specfiles but I don't really understand the way it works out.
I suspect its described on the wiki, but I couldn't find it.
As an example, I maintain sleuthkit. Looking in 3 repos I see:
sleuthkit | 3.2.3-10.1 | x86_64 | security sleuthkit | 3.2.3-3.5 | x86_64 | factory-oss sleuthkit | 3.2.3-2.1.3 | x86_64 | openSUSE Current OSS
As of a few days ago, they all had "release: 0" in their respective specfiles.
My understanding is that the number following the dash above is the release number, I really have 3 releases of 3.2.3 represented above. -2, -3, and -10. Is that right?
If I push the code in security to factory, will it suddenly become -10 (or -11)?
Do I ever need to set the release value in my specfiles to anything but 0?
No, OBS is setting the release number during build to a proper value. However, it is important that you have a branch (or link) in your package sources, so OBS can ensure that your development version is always higher then the version in your submit target. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de