On Sat, Jul 10, 2010 at 9:41 PM, Anas Nashif <[email protected]> wrote:
> On 2010-07-10, at 4:36 AM, Felipe Contreras wrote:
>> On Sat, Jul 10, 2010 at 2:40 AM, Christian Daudt <[email protected]> wrote:
>>>
>>> I just read the Meego packaging guidelines and is says that there is
>>> no need for the %{dist} macro, not that it is prohibited.
>>
>> Yes, but Anas Nashif keeps rejecting my packages because of it:
>> http://lists.meego.com/pipermail/meego-commits/2010-July/000948.html
>
> Because you want to follow every single guideline out there, but not we have
> we established for meego, even after this has been clarified in the "internal
> discussion", you still submitted without .changes file.
Read above; we are not talking about %changelog, but the %{dist} tag.
This is what the guideline says:
---
There is no need for the %{dist} macro in the release field. This is
also handled directly by the build system.
---
Do you interpret that as "the %{dist} macro should not be present"?
> Nothing is set in stone, and I am sure the discussion we are having will just
> help improve things, but you cant just force your thinking and way of work on
> an established process, even if it is not perfect.
>
> So please follow the guidelines we have now and if we agree on something
> else, it will be valid for everybody and not only for you.
The guideline allows the %{dist} macro, you are interpreting it wrong.
And the guideline doesn't say *anything* regarding the %changelog section.
--
Felipe Contreras
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
