> > 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.
I eventually did that, I folded both BuildRequires into a single one for selinux-policy-devel and it worked just fine. > If you have any more issues with shipping custom policy, feel free to CC > me so that I get to you sooner. I think I really don't want the BuildRequires from the macro, they look superfluous since my build is passing and I certainly don't want to drag git needlessly in my buildroot. The Requires on the other hand are a must, so many thanks for the macro. One thing that I love is the ability to manage multiple modules at once. Unfortunately I didn't find how to break the line in the RPM spec: > %selinux_modules_install %{_datadir}/selinux/%{selinuxtype}/mod1.cil > %{_datadir}/selinux/%{selinuxtype}/mod2.pp Breaking the line with back-slashes didn't work, the modules weren't considered arguments to the macro: > %selinux_modules_install \ > %{_datadir}/selinux/%{selinuxtype}/mod1.cil \ > %{_datadir}/selinux/%{selinuxtype}/mod2.pp I tried %{selinux_modules_install} and other shenanigans but no luck. I can live with a long line every now and then :) 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