paxctl only does PT_PAX and not XATTR_PAX markings. paxctl-ng (from the sys-apps/elfix package) does do both, but can be built to do only one or the other. Finally XATTR_PAX markings can be also done via setattr. pax-mark from the pax-utils.eclass has the intelligence to best decide which to use and so one should not call any of these directly. In cases where pax-mark is not appropriate, eg in build systems, then paxmark.sh (also from sys-apps/elfix) should be used which provides the same intelligence as the eclass. This is a tracker, so please open new bugs for each individual package. Reproducible: Always
can we close this since we have no dependencies open?
(In reply to Matthew Thode ( prometheanfire ) from comment #1) > can we close this since we have no dependencies open? did you grep the tree to check? if yes, do it.
I just grepped through and filed bugs / fixed the one that was maint-needed. Mono is the only outstanding one that is wrong. there are a few old ebuilds still in the tree that use paxctl directly (wine and icedtea) but both have later versions that are fixed and at the same keywords, do we care about the old versions?
(In reply to Jason Zaman from comment #3) > I just grepped through and filed bugs / fixed the one that was maint-needed. > > Mono is the only outstanding one that is wrong. > > there are a few old ebuilds still in the tree that use paxctl directly (wine > and icedtea) but both have later versions that are fixed and at the same > keywords, do we care about the old versions? what a grep misses is build systems that use paxctl rather than paxmark.sh. Let's leave this open for a while.
Can you define "a while"? 3+ years good enough?
