Re: [gentoo-dev] RFC: ban EAPI 1

[Ulrich Mueller <ulm@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

>>>>> On Thu, 11 Jun 2015, Alexis Ballier wrote:

>> dev-lang/ocaml-3.12.1                   in slot

> in subslot not slot, but more importantly in stable

Right, there are newer ebuilds in slot 0 for dev-lang/ocaml. I've
double-checked the list now; for all other packages the "in slot" was
accurate.

>> Maintainers can still use --force if there is no other way.

> i'm definitely not convinced it is good practice to encourage people
> to do that ;)

People are strongly encouraged to update their ebuilds to a newer
EAPI. ;) There are few EAPI 1 ebuilds left and the point is to prevent
adding new ones accidentally.

> also, it seems eapis-banned is not just about new ebuilds but also
> when there happens to be an ancient ebuild in the same directory

Yes, and that repoman behaves this way is the very reason why EAPIs
1 and 2 haven't been banned already one year ago. After all, this was
a council decision:
https://projects.gentoo.org/council/meeting-logs/20140225.txt

Ulrich

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]