What's the best way to get rid of deprecated ebuilds? Do we just wait for their maintainers to migrate them or should they be sought out and flagged? I'm pondering searching for EAPI 0 ebuilds and filing bug reports on them.
On Sun, Aug 16, 2015 at 6:57 AM, Rich Freeman <ri...@gentoo.org> wrote: > On Sun, Aug 16, 2015 at 9:47 AM, "Paweł Hajdan, Jr." > <phajdan...@gentoo.org> wrote: > > On 8/16/15 3:29 PM, Rich Freeman wrote: > >> They are deprecated already: > >> https://gitweb.gentoo.org/repo/gentoo.git/tree/metadata/layout.conf > >> > >> Deprecated means stop adding them, and move away from them. Repoman > >> will give you a warning about them. > > > > Is anything blocking deprecating EAPI4 in the same way? > > > > Not that I'm aware of, and it is probably something worth discussing > at this point. Moving to EAPI5 has some user-visible improvement for > many packages, like slot-operator dependencies. EAPI6 will also have > a user-visible improvement in forced support for user-patching for all > ebuilds (any ebuild can support user-patches now, but it isn't > mandatory). So, more than in the past it is useful to nudge devs > along to the most recent EAPIs (in the past they've been more about > maintainability and less user-visible). > > -- > Rich > >
