On Tue, Jun 22, 2021 at 12:06 PM Ulrich Mueller <u...@gentoo.org> wrote: > > >>>>> On Tue, 22 Jun 2021, Marek Szuba wrote: > > > Seeing as in the end this USE flag is not going anywhere in spite of > > Gentoo no longer providing PaX-capable kernel sources, could we please > > rename it (e.g. to 'pax-kernel') so that it no longer contains a > > disallowed character. I understand the main reason this hasn't been > > done yet is that we expected it might disappear altogether. > > +1 for renaming to pax-kernel. > > A related question, the pax_kernel flag is still used by these packages: > > app-emulation/virtualbox > app-emulation/virtualbox-modules > dev-java/icedtea > dev-lang/mlton > dev-lang/mono > dev-lang/smlnj > dev-libs/libffi > dev-libs/libffi-compat > media-sound/spotify > net-libs/nodejs > > From my past experience with PaX support in Emacs, things used to break > on a regular basis [1]. So I wonder, how is the status of PaX support in > the packages listed above? Do their maintainers actually test them with > a PaX kernel (which would be a third-party kernel, I suppose)? If not, > maybe the flag should be removed from these untested packages?
ebuild maintainers are rarely responsible for the PaX-related workarounds that end up in ebuilds. A better question would be if *anybody* is using these packages with a PaX-enabled kernel, and that's more difficult to answer.
