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