On Thu, 2014-11-06 at 17:18 +0100, Dominig ar Foll wrote:
> Best practice is to defined option variable via %bcond as it allows to
> read the default options in an easy way and they can be changed in the
> rpm command line and add a comment in the spec file.
So bcond is staying as the recommended approach?
I remember an Intel-internal discussion where it was pointed out that
when inheriting from a project in OBS, the choice of the parent project
for enabling or disabling something cannot be overridden anymore when
using bcond.
Ed Bartosh then proposed to use simple macros instead of bconds. Instead
of:
%if %{with pulseaudio_samsung_policy}
the spec file would use:
%if 0%{?_with_pulseaudio_samsung_policy}
Is that proposal dead?
> For more info of rpm behaviour see :
> https://en.opensuse.org/openSUSE:Build_Service_prjconf#Macros
For Tizen, https://wiki.tizen.org/wiki/Packaging/Guidelines is the only
(?!) page we have that explains what a spec file for Tizen should look
like.
Unfortunately a lot of information is missing:
* bconds not mentioned at all
* no list of recommended and/or available macros
For example, how is one supposed to know that %cmake is better than just
cmake, or that %{_docdir}/.. should better be %{_datadir}/doc?
I would update the page, except that I don't know the answers. Who does?
Regarding bconds or macros (whatever we use), we should maintain a list
of them in the Wiki. I volunteer to populate the list by grepping
existing .spec files, but first we should clarify what the desired
approach is.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
