From: Sam James <sam@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org, gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev-announce] EAPI 8 is here!
Date: Thu, 17 Jun 2021 00:10:26 +0100 [thread overview]
Message-ID: <BEB38A2D-1F13-4639-9F08-3F2C8402E4B7@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2686 bytes --]
Hi!
EAPI 8 is here! In fact, it arrived a few days ago on Sunday:
1) Council approval of EAPI 8 on Sunday at the regular meeting
2) Swift release of Portage 3.0.20 containing EAPI 8 by Zac shortly thereafter.
Summary:
* mgorny's traditional summary is already out and can be found on his website [0].
* PMS has been updated officially and can be found in PDF [1] or HTML [2] format,
or even a cheat sheet [3].
* Brings IDEPEND, usev enhancements, --disable-static by default, and more!
Things you need to know:
* You can read the full specification in PMS as above.
* It's fully implemented in Portage 3.0.20, pkgcore 0.12.0, and pkgcheck 0.10.0.
* You can use it *today* in ~arch ebuilds but will not be able to stabilise them
until Portage 3.0.20 is itself stabilised.
* base-system@ packages will not be using it for some time (a year), with possibly
some exceptions for special cases. [4].
Note about eclasses:
* Most eclasses *do not* yet support EAPI 8.
* During the council meeting, the council endorsed the following statement:
"We should try clean up eclasses before adding EAPI 8 support to them. This includes adding future EAPI guards on changes,
but also clean up indirect inherits and so on. We encourage people to put the EAPI 8 support patches to the ML, even if it's e.g.
cmake.eclass (which is sometimes seen as kde@'s purview), in order to ensure we maximise such opportunities."
I therefore kindly ask eclass maintainers and contributors alike to post all patches for eclasses adding EAPI 8 support
even if they appear trivial to allow us to make much needed improvements which otherwise would need to wait for the
next EAPI (this is because we can get away with changing some behaviour like e.g. indirect inherits given the ebuild
Is being tested for the first time with the new EAPI by maintainers once support gets added.)
You can see mgorny's email to gentoo-dev with the summary pre-approval [5] too.
Any questions? Reply to this email, PM me, or ask me on #gentoo-dev or #gentoo-dev-help. Or ask anyone else, of course.
TL;DR: EAPI 8 is here, you can use in in ~arch now, it has some neat improvements which make ebuilds cleaner, and brings
IDEPEND to the table. Read the full specification or mgorny's summary for the details.
[0] https://mgorny.pl/articles/the-ultimate-guide-to-eapi-8.html
[1] https://projects.gentoo.org/pms/8/pms.pdf
[2] https://projects.gentoo.org/pms/8/pms.html
[3] https://projects.gentoo.org/pms/8/eapi-cheatsheet.pdf
[4] https://wiki.gentoo.org/wiki/Project:Base#Rules_and_limitations
[5] https://archives.gentoo.org/gentoo-dev/message/8944c341d9353af0081180407dc7c14f
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
reply other threads:[~2021-06-16 23:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BEB38A2D-1F13-4639-9F08-3F2C8402E4B7@gentoo.org \
--to=sam@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-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