I noticed while working on open permissions that checkmodule actually is being linked statically to libsepol.a. Why? This means that when adding a new capability in libsepol we have to recompile checkpolicy. Just wondering why we do it this way. -Eric 'does not know the toolchain' Paris -- 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.
