Re: Use of optional_policy in templates (compiler bug or feature?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Oct 22, 2008, at 9:01 AM, Stephen Smalley wrote:

  I did notice however that I could also get it to build w/o
changing checkmodule by reversing the order of the interface calls there
- not sure if that workaround is usable in the original case that
triggered this bug report.


Arranging modules in the proper order becomes increasingly difficult as module interaction grows. I finally de-optioned the X policy in fedora since it is in base so get our additions to compile. Patch included for reference.

Making the compiler gracefully deal with options would really be appreciated. I could see the issue in the compiler code, but the right fix wasn't obvious.

joe

diff -up serefpolicy-3.5.10/policy/modules/system/userdomain.if.orig serefpolicy-3.5.10/policy/modules/system/userdomain.if --- serefpolicy-3.5.10/policy/modules/system/userdomain.if.orig 2008-10-20 14:14:37.000000000 -0500 +++ serefpolicy-3.5.10/policy/modules/system/userdomain.if 2008-10-20 14:27:37.000000000 -0500
 #######################################
@@ -658,9 +660,7 @@ template(`userdom_common_user_template',

        userdom_exec_generic_pgms_template($1)

-       optional_policy(`
-               userdom_xwindows_client_template($1)
-       ')
+       userdom_xwindows_client_template($1)

        ##############################
        #


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.

[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux