1) change ebuild.sh code to use selinux configuration to determine where the file contexts are, rather than a setting in make.conf. 2) change portage support to a FEATURE rather than USE. This enables the user to disable the portage support if their setup is broken, while still enabling selinux support in any packages they might merge. I was going to submit a patch for portage.py, but the place it needs to be changed (line 7234 in rev 1.524.2.76/2.0.53_rc6), features (the variable) isn't filled yet, so I was unsure of the proper fix.
Created attachment 71704 [details, diff] ebuild.sh-selinux.diff
Created attachment 71705 [details, diff] ebuild.sh-selinux.diff die correctly
assuming no complaints about a feature enabling a use flag, +1 on this. Others?
no, no, no, I don't want the feature enabling a use flag, I just want the code in portage to be controlled by the feature instead of the use flag. Both the use flag and the feature are turned on by default in the SELinux profiles.
ahh, convert strictly over to checking features, k.
*nudge* we're really going to be needing this update in the next month+, can it be merged?
added to svn trunk
This is in r2606 for release in 2.1_pre5.
Released in 2.1_pre5.
