From: konsolebox <konsolebox@gmail.com>
To: gentoo-dev@lists.gentoo.org
Cc: "Ulrich Müller" <ulm@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] glep-0083: New section "Support for EAPIs by package managers"
Date: Thu, 26 Jun 2025 11:54:40 +0800 [thread overview]
Message-ID: <CAJnmqwZFNZg9nA95_xfjQ-mZ_-wdKnN0ewSK4mg4Kt_0r0fosA@mail.gmail.com> (raw)
In-Reply-To: <20250619173354.22787-1-ulm@gentoo.org>
On Fri, Jun 20, 2025 at 1:34 AM Ulrich Müller <ulm@gentoo.org> 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.
--
konsolebox
next prev parent reply other threads:[~2025-06-26 3:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 17:33 [gentoo-dev] GLEP 83 update: Support for EAPIs by package managers Ulrich Müller
2025-06-19 17:07 ` [gentoo-dev] [PATCH] glep-0083: New section "Support for EAPIs by package managers" Ulrich Müller
2025-06-26 3:54 ` konsolebox [this message]
2025-06-26 5:19 ` Eli Schwartz
2025-06-26 13:48 ` Sam James
2025-06-26 16:25 ` Ulrich Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJnmqwZFNZg9nA95_xfjQ-mZ_-wdKnN0ewSK4mg4Kt_0r0fosA@mail.gmail.com \
--to=konsolebox@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ulm@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox