| 1 |
Michael Palimaka posted on Sat, 21 Sep 2013 23:27:07 +1000 as excerpted: |
| 2 |
|
| 3 |
> On 21/09/2013 10:49, Duncan wrote: |
| 4 |
>> In addition to what the others have said, FEATURES= ?? AFAIK, FEATURES |
| 5 |
>> is PM-implementation-specific and not part of PMS. It's not something |
| 6 |
>> ebuilds/eclasses should be messing with or care about at all, as it's |
| 7 |
>> PM-private-implementation domain, not ebuild domain. |
| 8 |
> Presumably he is talking about FEATURES in the context of adding them to |
| 9 |
> RESTRICT, which is discussed in PMS. |
| 10 |
|
| 11 |
That /does/ make a bit more sense, and I see others presumed it as well, |
| 12 |
but it was entirely missing from the OP, which really mixed me up, even |
| 13 |
after seeing discussion of RESTRICT in the replies, since that seemed to |
| 14 |
come from nowhere. |
| 15 |
|
| 16 |
> (Not that it really matters anyway - there are plenty of non-PMS |
| 17 |
> variables used in ebuilds. That's fine, they control portage features |
| 18 |
> and will be ignored by other package managers.) |
| 19 |
|
| 20 |
True. I guess it's nothing to worry about as long as the ebuild isn't |
| 21 |
depending on the implementation-specific var for anything vital to the |
| 22 |
package, only optional bits. |
| 23 |
|
| 24 |
Thanks. Clearer now. =:^) |
| 25 |
|
| 26 |
-- |
| 27 |
Duncan - List replies preferred. No HTML msgs. |
| 28 |
"Every nonfree program has a lord, a master -- |
| 29 |
and if you use the program, he is your master." Richard Stallman |
Archives