| 1 |
>>>>> On Thu, 11 Jun 2015, Alexis Ballier wrote: |
| 2 |
|
| 3 |
>> dev-lang/ocaml-3.12.1 in slot |
| 4 |
|
| 5 |
> in subslot not slot, but more importantly in stable |
| 6 |
|
| 7 |
Right, there are newer ebuilds in slot 0 for dev-lang/ocaml. I've |
| 8 |
double-checked the list now; for all other packages the "in slot" was |
| 9 |
accurate. |
| 10 |
|
| 11 |
>> Maintainers can still use --force if there is no other way. |
| 12 |
|
| 13 |
> i'm definitely not convinced it is good practice to encourage people |
| 14 |
> to do that ;) |
| 15 |
|
| 16 |
People are strongly encouraged to update their ebuilds to a newer |
| 17 |
EAPI. ;) There are few EAPI 1 ebuilds left and the point is to prevent |
| 18 |
adding new ones accidentally. |
| 19 |
|
| 20 |
> also, it seems eapis-banned is not just about new ebuilds but also |
| 21 |
> when there happens to be an ancient ebuild in the same directory |
| 22 |
|
| 23 |
Yes, and that repoman behaves this way is the very reason why EAPIs |
| 24 |
1 and 2 haven't been banned already one year ago. After all, this was |
| 25 |
a council decision: |
| 26 |
https://projects.gentoo.org/council/meeting-logs/20140225.txt |
| 27 |
|
| 28 |
Ulrich |
Archives