The ebuild has: if use pax_kernel; then pax-mark m "${ED}"usr/bin/orc-bugreport pax-mark m "${ED}"usr/bin/orcc pax-mark m "${ED}"usr/$(get_libdir)/liborc*.so* fi However, the pax-mark function handles missing tooling gracefully, and hardened profiles guarantee that the tooling is installed. Given that the majority of packages calls pax-mark unconditionally, is there a reason not do the same here?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e3633014ee6b3f8d556d44cc59b5ec6ebf516504 commit e3633014ee6b3f8d556d44cc59b5ec6ebf516504 Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2019-11-21 19:39:26 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2019-11-23 21:41:20 +0000 dev-lang/orc: Version bump to 0.4.31 - Convert to Meson (autotools build system was removed) - EAPI=7 - Drop Darwin hack - Drop IUSE=pax_kernel Bug: https://bugs.gentoo.org/691804 Closes: https://bugs.gentoo.org/554600 Closes: https://bugs.gentoo.org/645232 Closes: https://bugs.gentoo.org/698272 Signed-off-by: Matt Turner <mattst88@gentoo.org> dev-lang/orc/Manifest | 1 + dev-lang/orc/orc-0.4.31.ebuild | 43 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 44 insertions(+)
