public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] EAPI 6 portage is out!
Date: Tue, 17 Nov 2015 20:04:30 -0500	[thread overview]
Message-ID: <564BCE9E.6050403@gentoo.org> (raw)
In-Reply-To: <564BAE1D.5090103@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 17/11/15 05:45 PM, Michael Orlitzky wrote:
> On 11/17/2015 05:09 PM, Michał Górny wrote:
>> 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.
>> 
> 
> Thanks for all the work on this and the guide.
> 
> Is it really safe to start committing ~arch ebuilds that don't
> work with stable portage? Might not things get wonky for stable
> users who have a few keyworded packages?
> 
> For developers, is my stable version of repoman smart enough to
> make sure I don't break any dependencies in this way?
> 
> 

If your PM doesn't support EAPI6, then those ebuilds will be ignored
just as if they do not exist.  It is plenty safe.  There can be
issues if EAPI5 or older ~arch packages start -needing- EAPI6-only
~arch dependencies, but so long as people are careful (and likely,
start bumping to EAPI6 along with the dependencies) then things will
work out without much incident.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EAREIAAYFAlZLzp4ACgkQAJxUfCtlWe00AAEA5RoB95Z/pvQcqYu+1dDzPh2d
/MP+kcQdHus14B+SnMsBANZubHScfv/9z75lY3Hub3GnamyPLgtSDGyK43UatKBv
=m7RY
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2015-11-18  1:04 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17 22:09 [gentoo-dev] EAPI 6 portage is out! Michał Górny
2015-11-17 22:45 ` Michael Orlitzky
2015-11-17 23:35   ` Mike Gilbert
2015-11-18  1:04   ` Ian Stakenvicius [this message]
2015-11-18  2:22     ` Michael Orlitzky
2015-11-18  7:25       ` Ulrich Mueller
2015-11-18  9:25         ` Alexander Berntsen
2015-11-18  9:54           ` Raymond Jennings
2015-11-19  8:13             ` Daniel Campbell
2015-11-18 11:05           ` Ulrich Mueller
2015-11-18 11:12             ` Alexander Berntsen
2015-11-18 11:23               ` Ulrich Mueller
2015-11-18 11:26                 ` Alexander Berntsen
2015-11-18 12:01               ` Rich Freeman
2015-11-18 12:06                 ` Alexander Berntsen
2015-11-18 12:48                   ` Rich Freeman
2015-11-21  4:35                   ` Daniel Campbell
2015-11-20  9:39                 ` Patrick Lauer
2015-11-20 12:34                   ` Rich Freeman
2015-11-21 18:51                 ` Andrew Savchenko
2015-11-21 21:00                   ` Rich Freeman
2015-11-22 15:54                   ` [gentoo-dev] " Michael Palimaka
2015-11-22 16:29                     ` Dirkjan Ochtman
2015-11-22 16:41                     ` Andreas K. Huettel
2015-11-23  7:26                     ` Duncan
2015-11-18 15:09               ` [gentoo-dev] " Andreas K. Huettel
2015-11-18 11:59             ` Rich Freeman
2015-11-18 12:00               ` Alexander Berntsen
2015-11-18 15:10               ` Brian Dolbec
2015-11-18 16:47                 ` Rich Freeman
2015-11-20  9:27                   ` Ian Delaney
2015-11-18 16:47             ` [gentoo-dev] " »Q«
2015-11-18 17:06               ` Ulrich Mueller
2015-11-18 17:56                 ` »Q«
2015-11-18 14:57           ` [gentoo-dev] " Andreas K. Huettel
2015-11-18 18:50         ` Ian Stakenvicius
2015-11-18 19:17           ` Andreas K. Huettel
2015-11-18  1:54   ` [gentoo-dev] " Duncan
2015-11-18  3:15     ` Rich Freeman
2015-11-18  1:20 ` [gentoo-dev] " NP-Hardass
2015-11-18  5:10   ` Michał Górny
2015-11-22  8:19 ` [gentoo-dev] " Martin Vaeth

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=564BCE9E.6050403@gentoo.org \
    --to=axs@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