public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] EAPI 7 can be used in the Gentoo repository
Date: Sun, 6 May 2018 17:37:30 +0000	[thread overview]
Message-ID: <712f856056e6a2492acdb82ec3da9762a5756dd6.camel@infinera.com> (raw)
In-Reply-To: <23279.12986.956905.567730@a1i15.kph.uni-mainz.de>

[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]

Great news :)

W.r.t the new support for cross building, it would be grep if the eclass user could make use of
the new --prefix support in recent shadow utilities so users can be added to cross ROOT.

Jocke

On Sun, 2018-05-06 at 18:52 +0200, Ulrich Mueller wrote:
EAPI 7 has been approved by the Council one week ago [1]. The latest
Portage version in ~arch (2.3.36) supports it, and the Infra team has
upgraded the rsync master so that metadata cache generation will work
correctly.

Therefore, EAPI 7 ebuilds can be committed to the Gentoo repository
from now on. (Make sure that all inherited eclasses are supporting the
new EAPI, though.)

Some pointers to documentation:

- Package Manager Specification, in PDF and HTML format:
  https://projects.gentoo.org/pms/latest/
  or install ~app-doc/pms-7_p20180430

- List of changes in EAPI 7:
  https://projects.gentoo.org/pms/7/pms.html#x1-179000E

- EAPI Cheat Sheet (print out, and fold to a leaflet):
  https://projects.gentoo.org/pms/7/eapi-cheatsheet.pdf

- mgorny's (unofficial) guide:
  https://dev.gentoo.org/~mgorny/articles/the-ultimate-guide-to-eapi-7.html

Ulrich

[1] https://bugs.gentoo.org/654262


[-- Attachment #2: Type: text/html, Size: 2016 bytes --]

  reply	other threads:[~2018-05-06 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-06 16:52 [gentoo-dev] EAPI 7 can be used in the Gentoo repository Ulrich Mueller
2018-05-06 17:37 ` Joakim Tjernlund [this message]
2018-05-06 18:43   ` Geaaru
2018-05-06 21:03     ` Zac Medico

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=712f856056e6a2492acdb82ec3da9762a5756dd6.camel@infinera.com \
    --to=joakim.tjernlund@infinera.com \
    --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