20:03 <@SwifT> feandil: not really, if the strict & mls policy deployments are both handled by gentoo still (so they are both in POLICY_TYPES) then the directory for strict and for mls will be the same, so the change in sepolgen.conf is not needed 20:05 <@SwifT> feandil: but if you switch from strict to mls, update POLICY_TYPES and pull in more policy changes (ebuilds), then as long as sepolgen.conf isn't updated, it might eventually give issues 20:05 <@SwifT> feandil: so I might need to update the file upon selinux-base builds 20:05 <@SwifT> haven't put that in yet 20:05 <@SwifT> i'll bug myself for it - at least an ewarn would be nice In other words, try to detect if a policy name change has occurred (parse sepolgen.conf?) and if so, warn the user that sepolgen.conf needs to be updated. Reproducible: Always
I'm probably going to add in a pkg_setup() that generates the SELINUX_DEVEL_PATH entry (similar as how dev-python/sepolgen does it) and check if the line in /etc/selinux/sepolgen.conf is correct, and warn the user if that is not the case.
Hmm, perhaps it would work to set a symbolic link (/usr/share/selinux/current or devel) to the currect location. That would make it a lot simpler. I'll check that out later.
xapi ~ # sepolgen File "/usr/lib/python-exec/python3.4/sepolicy", line 265 print "\n" + bold_start + "%s: %s %s" % (src, protocol, perm) + bold_end ^ SyntaxError: invalid syntax (still?)
