>>>>> On Tue, 27 Jan 2026, Eli Schwartz wrote: > On 1/27/26 1:50 AM, Michał Górny wrote: >> Please don't commit these yet. I'm planning to have another look at the >> eclasses, since they need more cleanup, and do a proper EAPI 9 series >> for them.
> I'm not in a tremendous hurry, but please note my goal was > incrementalism. If we aren't ready for adding EAPI 9, but have other > patches to push in the meantime, these are 100% safe to apply as part > of the next batch, solely for EAPI 8. As I said before, I think it is pointless to add the eapi9-pipestatus workaround for EAPI 8 now, when EAPI 9 is already available. The whole endeavour was triggered by the work on EAPI 9, and the eapi9-pipestatus eclass wouldn't even exist without it. IMHO the more logical path would be to combine these changes with enabling of EAPI 9 support in these eclasses. It would also save a round of metadata recreation. Ulrich
signature.asc
Description: PGP signature
