| 1 |
Jeremy Olexa posted on Thu, 05 Aug 2010 18:43:55 -0500 as excerpted: |
| 2 |
|
| 3 |
> People will not "hate you" - if the portage with EAPI4 is in ~arch, you |
| 4 |
> can have PHP w/EAPI4 in ~arch, even on zero-day of release. Likewise |
| 5 |
> with stable tree. It does not matter when council "approves" EAPI4, it |
| 6 |
> matters when portage has the implementation and is released.. |
| 7 |
|
| 8 |
Isn't it /both/? IOW, just because portage implements it, doesn't mean |
| 9 |
it's usable in-tree, if it's not part of an approved EAPI. Similarly, |
| 10 |
approval before released support again doesn't mean it's allowed in-tree. |
| 11 |
Only with both is it then allowed. |
| 12 |
|
| 13 |
Leastwise, that was my read of the council decision back then. |
| 14 |
|
| 15 |
But zero-day, yes, provided it's both approved and in-portage at the same |
| 16 |
level (~arch or stable). |
| 17 |
|
| 18 |
> The caveat is with @system packages, especially bash/python/portage |
| 19 |
> itself. |
| 20 |
|
| 21 |
Again, yes. |
| 22 |
|
| 23 |
-- |
| 24 |
Duncan - List replies preferred. No HTML msgs. |
| 25 |
"Every nonfree program has a lord, a master -- |
| 26 |
and if you use the program, he is your master." Richard Stallman |
Archives