On 10/16/15 7:49 PM, Peter Stuge wrote:
Anthony G. Basile wrote:
if you emerge when using a vanilla kernel or some other which doesn't
support user.pax.* on tmpfs, then you'll loose those markings.
Would it be at all possible to add the markings after/as files land
on the destination filesystem instead?
first, I overspoke. that line should read "you might loose those markings".
since we sometimes have to do pax markings during src_compile() or
src_test() or early during src_install() etc, the safest approach is to
preserve xattrs at every step of the process. so we wrote a wrapper on
install for that and made sure portage provided end-to-end xattr
support. this doesn't prevent an ebuild from also doing the markings
again during pkg_postinst() after the file(s) lands just in case.
It's not really intuitive that tmpfs on the emerging kernel must
support a feature at build-time which is used by the runtime kernel
at run-time..
And what about stages? tar saves all attributes? It's a bit weak to
be less flexible than that.
we made sure catalyst will preserve xattrs when bundling.
Thanks
//Peter
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : [email protected]
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
