From: Sam James <sam@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [RFC] LTS branch of Portage
Date: Wed, 20 Oct 2021 10:24:47 +0100 [thread overview]
Message-ID: <2A86B021-688D-4FBE-9D59-0C0259AFB4D8@gentoo.org> (raw)
In-Reply-To: <CAD6zcDwpOH8w6jshUdMPkXPD2Q6_bccqPkrHgZ6tOacLst2DrA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
> On 19 Oct 2021, at 00:24, Francesco Riosa <vivo75@gmail.com> wrote:
>
> Sorry but portage is too strictly related to the ebuilds in tree, recent removal of EAPI=5 from most eclasses underlined that.
> Or to put id differently if you want a LTS portage you also need a certain number of "protected" eclasses and ebuilds
> It seems a lot of (very appreciated but don't count on me) work
FWIW, I don't think it'd be a big deal to just agree that we wouldn't rip out old EAPI support from eclasses
and also slow down with adopting new EAPIs for ebuilds (which there's vague consensus about wrt EAPI 8
being done a bit too quickly anyway).
i.e. I don't think this is really a blocker.
Best,
sam
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
prev parent reply other threads:[~2021-10-20 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 8:31 [gentoo-portage-dev] [RFC] LTS branch of Portage Michał Górny
2021-10-05 8:41 ` Fabian Groffen
2021-10-05 14:15 ` Michael Orlitzky
2021-10-05 15:13 ` Michał Górny
2021-10-05 17:16 ` Michael Orlitzky
2021-10-05 17:30 ` Michał Górny
2021-10-06 2:36 ` Alec Warner
2021-10-18 23:24 ` Francesco Riosa
2021-10-19 23:43 ` Alec Warner
2021-10-20 9:24 ` Sam James [this message]
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=2A86B021-688D-4FBE-9D59-0C0259AFB4D8@gentoo.org \
--to=sam@gentoo.org \
--cc=gentoo-portage-dev@lists.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