From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Cc: <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev-announce] EAPI 6 portage is out!
Date: Tue, 17 Nov 2015 23:09:34 +0100 [thread overview]
Message-ID: <20151117230934.15218644.mgorny@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
Fellow Developers!
I have the pleasure to announce that portage-2.2.25 has just been
committed and it comes with complete EAPI 6 support. This effectively
means that from this moment forward Gentoo developers are permitted to
commit EAPI 6 ebuilds to ~arch.
Some quick notes:
1. Remember that you can't stabilize ebuilds using EAPI 6. Therefore,
if you go for EAPI 6, you ebuild may be forced to stay ~arch for quite
a while.
2. The Portage implementation needs more testing and can be buggy.
Write ebuilds according to the spec, not Portage behavior or they will
fail.
2a. It just occurred to me that Portage does not fail when eapply_user
is not called. This is a bug, so make sure to call it or
default_src_prepare.
3. EAPI 6 is not a drop-in replacement for EAPI 5. Study it to use it
efficiently. Use it as an opportunity to improve the API of your
eclasses.
4. I've written an extensive guide [1] with some explanations
and rationale for many of the features. Consider it a must-read.
4a. We need someone to update the devmanual.
[1]:https://blogs.gentoo.org/mgorny/2015/11/13/the-ultimate-guide-to-eapi-6/
--
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
reply other threads:[~2015-11-17 22:10 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=20151117230934.15218644.mgorny@gentoo.org \
--to=mgorny@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