On Thu, Jun 11, 2015 at 12:55 PM, Alexis Ballier <aball...@gentoo.org> wrote: > On Thu, 11 Jun 2015 18:33:36 +0200 > Ulrich Mueller <u...@gentoo.org> wrote: > >> >> 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 > > > i agree, but what worries me is that you suddenly introduced repoman > errors for a bunch of packages for which there is no clear ETA on when > these can be fixed (i think qa policy is to not bump eapi in place) > > this is not just about "fixing" a line in an ebuild, it is about proper > testing for stabilization and e.g. ocaml is definitely not a package > whose stabilization should be done lightly >
These errors are not user-visible. I really don't have a problem with repoman errors for deprecated features. We've been discouraging EAPI 1 for a while now. This just raises the volume a bit, while still not creating any hard problems during the transition. Sure, it would be nice if repoman only complained for new ebuilds, since that is the policy, but honestly making noise about old ones is probably useful, just so that we can keep their removal on the radar. Also, EAPI 1 and 2 WERE banned by the Council. Whether or not repoman's settings were adjusted has nothing to do with the fact that they were banned for new ebuilds. -- Rich
