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