| 1 |
>>>>> On Thu, 29 May 2014, Andreas K Huettel wrote: |
| 2 |
|
| 3 |
> Let's decide that the maximum number of EAPIs allowed in the portage |
| 4 |
> tree at any time must not exceed 7. |
| 5 |
|
| 6 |
> 7, since then EAPI=6 can still go ahead as planned. |
| 7 |
|
| 8 |
> Any new plans afterwards can only proceed if EAPI=1 is finally gone |
| 9 |
> (achievable), and for more improvements the bar gets a bit higher |
| 10 |
> afterwards. |
| 11 |
|
| 12 |
That's tree policy, but doesn't prevent PMS and package managers from |
| 13 |
supporting more than that number of EAPIs. |
| 14 |
|
| 15 |
In fact, we could finalise the new EAPI, but devs would only be |
| 16 |
allowed to commit such ebuilds to the tree when one of the old EAPIs |
| 17 |
is gone. Nice way to increase peer pressure. :-) |
| 18 |
|
| 19 |
Ulrich |
Archives