| 1 |
On Montag, 16. August 2021 19:06:28 CEST Joonas Niilola wrote: |
| 2 |
> On 16.8.2021 19.53, Marek Szuba wrote: |
| 3 |
> > On 2021-08-16 17:49, Sam James wrote: |
| 4 |
> >> See https://bugs.gentoo.org/802786 and |
| 5 |
> >> https://github.com/gentoo/kde/pull/903. There's some work to be done |
| 6 |
> >> first. |
| 7 |
> > |
| 8 |
> > I see. Guess we'll have to stick with EAPI 7 for cmake revdeps in the |
| 9 |
> > foreseeable future, then. |
| 10 |
> |
| 11 |
> What's the rush with 8 anyway? We still have eclasses that don't even |
| 12 |
> support 7. And since 6 is now, sigh, deprecated, any bump to ebuilds |
| 13 |
> depending on those eclasses will add to the evergrowing CI issue list |
| 14 |
> right? I'd say it's more important to secure EAPI-7 support there first. |
| 15 |
> |
| 16 |
> -- juippis |
| 17 |
|
| 18 |
I daresay eclasses still missing EAPI-7 support at this point comprise of |
| 19 |
abandonware. We are at 81% >=EAPI-7 coverage among all ebuilds. |
| 20 |
|
| 21 |
cmake.eclass has zero <EAPI-7 consumers and all its deps are ready, so it is |
| 22 |
only logical to gain EAPI-8 support soon. |
| 23 |
|
| 24 |
Regards |
Archives