On 05. 04. 19 15:58, Dridi Boukelmoune wrote:
On Fri, Apr 5, 2019 at 3:36 PM Dridi Boukelmoune
<dridi.boukelmo...@gmail.com> wrote:
I think I found the solution here:
https://fedoraproject.org/wiki/PackagingDrafts/SELinux_Independent_Policy
BuildRequires: selinux-policy
%{?selinux_requires}
This way its expansion can be deferred at rebuild time, I suppose. But
don't we miss the other BuildRequires tags in this case?
We do:
make: /usr/share/selinux/devel/Makefile: No such file or directory
A different catch 22 now :(
I ended up with this, and it seems to cover all my needs:
BuildRequires: selinux-policy
BuildRequires: /usr/share/selinux/devel/Makefile
Thank you for the feedback. You are correct that the BuildRequires in
the macro are useless. At this point I have no idea how to get around
the macro expansion. I will at least add selinux-policy-devel package
BuildRequire to the Packaging guidelines.
If you have any more issues with shipping custom policy, feel free to CC
me so that I get to you sooner.
Vit
%{?selinux_requires}
I'm a bit curious on how things could improve on epel7, but having the
macros in the first place is already very helpful!
Dridi
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
