Anthony G. Basile wrote: >> Would it be at all possible to add the markings after/as files land >> on the destination filesystem instead? .. > 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.
I guess I'm suggesting to do so automatically, if markings were added (maybe only when unsuccessfully) in any of the previous steps, presumably involving tmpfs. >> 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. Cool - but! It all only works reliably if the build host runs a patched kernel, since it wraps portage, correct? Not as cool. //Peter
