| 1 |
Ciaran McCreesh posted on Wed, 04 Apr 2012 11:50:54 +0100 as excerpted: |
| 2 |
|
| 3 |
> On Wed, 04 Apr 2012 08:32:41 +0200 justin <jlec@g.o> wrote: |
| 4 |
>> 3. |
| 5 |
>> file capabilities (can this be done with portage) |
| 6 |
> |
| 7 |
> It can't. We've had discussions about caps before, and I imagine it |
| 8 |
> would get into EAPI 5 without objections if you can come up with a spec |
| 9 |
> that describes how it should work (bear in mind that some of the target |
| 10 |
> filesystems might not support caps). |
| 11 |
|
| 12 |
Isn't that what portage's xattr USE flag is all about, supporting caps, |
| 13 |
etc, via xattr? Altho as you said, it does require support on both |
| 14 |
PORTAGE_TMPDIR and the live filesystem. (I believe portage's install |
| 15 |
warns if the USE flag is on and either tmpfs or the live filesystem |
| 16 |
doesn't support it.) |
| 17 |
|
| 18 |
But that's a fairly new feature, probably not in stable, yet, and for all |
| 19 |
I know, 2.2 only. And while I guess a few packages support it via |
| 20 |
USE=caps, full and proper EAPI support couldn't be a bad thing. |
| 21 |
|
| 22 |
-- |
| 23 |
Duncan - List replies preferred. No HTML msgs. |
| 24 |
"Every nonfree program has a lord, a master -- |
| 25 |
and if you use the program, he is your master." Richard Stallman |
Archives