Hi,
Would you care to reply?
I think your interpretation of the %{dist} tag goes against the guidelines.
On Sat, Jul 10, 2010 at 12:12 PM, Felipe Contreras
<[email protected]> wrote:
> On Sat, Jul 10, 2010 at 7:44 AM, Anas Nashif <[email protected]> wrote:
>> On 2010-07-09, at 6:26 PM, Felipe Contreras wrote:
>>> OBS is also perfectly fine with the %{dist} tag as it's automatically
>>> dropped:
>>
>> Thats why it does not make any sense in meego :)
>
> I doesn't matter to MeeGo.
>
> What happens if I do:
> Releases: 1%{?dist} -> Nothing, OBS replaces it
> Releases: 0 -> Nothing, OBS replaces it
> Releases: wakawaka -> Nothing, OBS replaces it
>
> So what doesn't make sense in MeeGo is to enforce a guideline on the
> Releases field; if it's not used *at all*, people can put whatever
> they wan there. Why not allow something that other distros commonly
> use?
>
>> The problem is, if you have %{?dist}, then the original release number cant
>> be used, when you have a number, which is the standard, then obs takes it
>> and starts counting from there.
>
> So you are saying if it's a plain number, like 10, then OBS would
> replace it with something like 10.1? 10.1 -> 10.1.1?
>
> Well, in that case OBS can do s/%{?dist}//: and then OBS can use the
> release number: problem solved.
Wrong.
-----
I have the following modifications for dsp-tools.spec:
3c3
< Release: 1
---
> Release: 4.1
-----
See? OBS doesn't care what's in the Release field at all.
In fact the guideline kind of hints that:
---
This field is handled by the build system to be able to manage
automated builds. The initial setting in the spec file is used by the
build system but in many cases it does not need to be changed.
---
> And the guideline says:
> ---
> There is no need for the %{dist} macro in the release field. This is
> also handled directly by the build system.
> ---
>
> Which means %{?dist} is *not* forbidden.
>
>>>> bugs.meego.com
>>>
>>> I figured that much, but which component.
>
> Care to reply to this?
--
Felipe Contreras
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
