| 1 |
On Sat, 5 Mar 2011 18:41:46 +0100 |
| 2 |
Constanze Hausner <constanze@g.o> wrote: |
| 3 |
> > You're requiring special package manager behaviour if that flag is |
| 4 |
> > set? |
| 5 |
> |
| 6 |
> I'm requiring, that the package manager preserves the xattrs, when |
| 7 |
> stripping the binary and when moving it from the sandbox to the |
| 8 |
> live-fs. |
| 9 |
|
| 10 |
Currently we've got wording in PMS forbidding anything from relying |
| 11 |
upon xattrs being preserved correctly, since that's what Portage did |
| 12 |
when we wrote it. So if you're looking to change that, you'll need to |
| 13 |
EAPI control it. |
| 14 |
|
| 15 |
But it's not as simple as just requiring attributes to be preserved in |
| 16 |
future EAPIs, since: |
| 17 |
|
| 18 |
* some xattrs are fs specific |
| 19 |
|
| 20 |
* some xattrs (selinux?) can't be copied |
| 21 |
|
| 22 |
* some filesystems don't support xattrs at all, and the package manager |
| 23 |
needs to support installing to them, even if the user is building on |
| 24 |
a filesystem that does support it |
| 25 |
|
| 26 |
* tar and xattrs is a massive problem, so how do binaries work? |
| 27 |
|
| 28 |
I think it'd help if you provided a description of how all the above |
| 29 |
(plus the other issues that I've forgotten about) can be handled. |
| 30 |
|
| 31 |
-- |
| 32 |
Ciaran McCreesh |
Archives