[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse-packaging
Subject:    Re: [opensuse-packaging] How is the "release" value in the specfile supposed to be set?
From:       Peter Linnell <mrdocs () opensuse ! org>
Date:       2012-02-22 20:31:59
Message-ID: 4F4550BF.8020006 () opensuse ! org
[Download RAW message or body]

On 02/15/2012 02:17 PM, Ralf Lang wrote:
> Am 15.02.2012 22:33, 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?
>>
>> Thanks
>> Greg
> IIRC OBS handles the release number itself. When packaging by hand, you
> can use the release number to indicate patch levels or subsequent
> changes of packaging without changing version of the packaged software
> itself.
>

Yes, and I generally set Release:0 and forget it in my packages. I've 
not needed to change this unless working on some branched packages.

HTH,
Peter


-- 
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

[prev in list] [next in list] [prev in thread] [next in thread]