paxctl refuses to mark the skype binary when built with the qt-static USE flag. Please warn users and mark the flags as mutually exclusive. Reproducible: Always
putting a couple of notes here. I think we don't want to use the pax_kernel use flag (and make it so pax_kernel and qt-static are mutually exclusive). This is because I feel that pax_kernel may be used for xattr markings eventually and since pax_kernel apparently works with xattr pax markings it would cause sadness. In the near term we can probably mark it, when xattr markings become more common I think an ewarn or something may be needed to state the inconsistencies. blueness, what is the plan for xattr markings and the pax_kernel use flag?
well, I guess nobody wanted to hear this but Skype doesn't have a static version of it's 4.1.0.20 release which is now in Portage. so unless new skype is broken also for dynamic version, there is nothing left to do here now ...
+1 voice for xattr marks and unmasking. The ebuild could also allow the emerge if the kernel happens to have no CONFIG_PAX_NOEXEC. A hardened profile doesn't imply hardened sources, and hardened sources still do not 100% imply that PAX_NOEXEC is set.