| 1 |
On Tue, 19 Feb 2019 22:46:23 -0800 Matt Turner wrote: |
| 2 |
> On Tue, Feb 19, 2019 at 10:24 PM Ulrich Mueller <ulm@g.o> wrote: |
| 3 |
> > |
| 4 |
> > >>>>> On Wed, 20 Feb 2019, Matt Turner wrote: |
| 5 |
> > |
| 6 |
> > > Nearly all the work is just removing uses of autotools-multilib and |
| 7 |
> > > autotools-utils. The new code should work in EAPI 4 and 5. Don't add |
| 8 |
> > > support for EAPI 6; that ship has already sailed. |
| 9 |
> > |
| 10 |
> > AFAICS, adding EAPI 6 support wouldn't require any additional code? |
| 11 |
> |
| 12 |
> I think that is true. (I have no strong preference on whether to add |
| 13 |
> EAPI 6 support. I just figured that anything that gets an EAPI bump |
| 14 |
> now should go to the latest available) |
| 15 |
|
| 16 |
This is not always possible. E.g. I have a package with optional |
| 17 |
java support. Since java is still EAPI 6 I can't use EAPI 7. |
| 18 |
|
| 19 |
Best regards, |
| 20 |
Andrew Savchenko |
Archives