Would be nice to have release media with full xattrs support. It's very useful if you want to install preconfigured hardened system with xattr pax markings. At least utilities like rsync and tar should be compiled with USE=xattr. livecd ~ # rsync -X rsync: extended attributes are not supported on this client rsync error: syntax or usage error (code 1) at main.c(1435) [client=3.0.9]
I believe this should already be set in the hardened release. Normal profile doesn't enable xattrs but admincd is built with hardened profile and should be fine. Is this not enough? Should xattrs be enabled for all profiles?
This issue is related to bug 531788 (caps) and with having a custom portage config to switch USE flags. @release: should we enable xattrs in all stages?
(In reply to Jorge Manuel B. S. Vicetto from comment #2) > This issue is related to bug 531788 (caps) and with having a custom portage > config to switch USE flags. > > @release: > should we enable xattrs in all stages? We are increasingly using xattrs and now have end-to-end xattr support in portage. We should start moving in a direction where xattrs is enabled for all stages.
i've enabled this by default now: http://gitweb.gentoo.org/repo/gentoo.git/commit/?id=824d0647e08da946ec357e436038d795ac589fd4 was able to build stage1/2/3 and the attr/pyxattr packages were pulled in. this should start making its way out to release media.
