| 1 |
>>>>> On Sat, 21 Jul 2012, Andreas K Huettel wrote: |
| 2 |
|
| 3 |
> I would like to bring up for your next meeting agenda a vote on the adoption |
| 4 |
> of the following feature in EAPI 5: "Support package.use.stable.mask and |
| 5 |
> package.use.stable.force files in profile dirs that restrict the use flag |
| 6 |
> combinations only for stable packages". |
| 7 |
|
| 8 |
I'd much prefer if the council would vote on the tentative list of |
| 9 |
EAPI 5 features in one single meeting. Let's envisage this for the |
| 10 |
August or September meeting. |
| 11 |
|
| 12 |
> * I have posted two patches for PMS, describing the feature and then |
| 13 |
> restricting its usage to EAPI 5, see thread [2]. Short of rewriting |
| 14 |
> all of PMS, I've implemented all that was asked from me there. |
| 15 |
|
| 16 |
One thing that is still missing is a definition of the different |
| 17 |
stabilisation levels. This should be added to chapter 7 of PMS where |
| 18 |
the KEYWORDS variable is described. Shouldn't be difficult, as you can |
| 19 |
follow <http://devmanual.gentoo.org/keywording/>. |
| 20 |
|
| 21 |
> * As for a reference implementation, Zac's comment basically was |
| 22 |
> that it's not too hard to do, and I'm hoping for his support. |
| 23 |
|
| 24 |
I would feel better it the implementation was ready before the council |
| 25 |
had to decide on the feature. The long delay of EAPI 4 was mainly |
| 26 |
caused by implementations not being ready, and we shouldn't repeat |
| 27 |
this mistake. |
| 28 |
|
| 29 |
Ulrich |
Archives