| 1 |
On 2021-07-16 22:50, Sam James wrote: |
| 2 |
|
| 3 |
> But to introduce a fix, isn't it a _lot_ easier to do it at the point of a new EAPI? |
| 4 |
|
| 5 |
In general, IMHO only if we intend to preserve the old (incorrect) |
| 6 |
behaviour for older EAPIs - which in this particular case was not needed |
| 7 |
because I cannot think of someone having come to rely on the fact EAPI-7 |
| 8 |
ebuilds inheriting fortran-2 could not be cross-compiled. |
| 9 |
|
| 10 |
In this particular case, the patch I submitted for review earlier on |
| 11 |
today explicitly mentions neither EAPI 7 nor EAPI 8 - so not really, no. |
| 12 |
In fact, I would argue that in case of eclasses requiring more work to |
| 13 |
adapt to a new EAPI trying to fix old bugs at the same time could |
| 14 |
distract reviewers from the EAPI adaptation itself. |
| 15 |
|
| 16 |
-- |
| 17 |
Marecki |
Archives