On 6/25/25 11:54 PM, konsolebox wrote:
> On Fri, Jun 20, 2025 at 1:34 AM Ulrich Müller <[email protected]> wrote:
>> +Conversely, removing support for an EAPI from the package manager can
>> +be disruptive for users.  Unofficial overlays and private repositories
>> +often continue using older EAPIs long after their removal from the
>> +main tree.  Therefore, the timeline for dropping package-manager
>> +support is more generous than that for use of EAPIs in repositories.
> 
> What's the point of these supposedly generous long-term support for
> old EAPIs when you're dropping support for them in eclasses like
> distutils-r1?  It's all silly and pointless.
> 
> Yes I've heard there's no obligation for eclass maintainers to support
> old EAPIs.  Same point applies.  You might as well tell overlay owners
> to not use ::gentoo's eclasses so these supposedly "long-term" support
> become sensible.


Precisely because overlay owners sometimes wish to do so -- and one
thing they CANNOT replace in their overlay, is /usr/bin/emerge. But they
could, if they wished, copy eclasses and restore older EAPIs in their
copy. Or package tons of software that use Autotools to build C code and
have no need of eclasses.

This thread isn't really a good place to come in with a chip on your
shoulder about Gentoo Python.


-- 
Eli Schwartz

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to