From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] EAPI 6 portage is out!
Date: Wed, 18 Nov 2015 13:50:07 -0500 [thread overview]
Message-ID: <564CC85F.3060400@gentoo.org> (raw)
In-Reply-To: <22092.10244.685936.324131@a1i15.kph.uni-mainz.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 18/11/15 02:25 AM, Ulrich Mueller wrote:
>>>>>> On Tue, 17 Nov 2015, Michael Orlitzky wrote:
>
>> It doesn't seem that unlikely to me...
>
>> 1. Otherwise stable system with package "foo" keyworded as
>> ~arch.
>
>> 2. foo needs some dependency of a dependency named "bar".
>
>> 3. The bar maintainer revbumps and removes the old EAPI=5
>> ebuild.
>
>> I don't really care either way, I'm just wondering whether this
>> is "safe" because it's actually safe, or "safe" because we're
>> gonna do it anyway.
>
> Actually it is quite simple:
>
> - The stable tree should not contain any EAPI 6 ebuilds at this
> point, so stable users should not see any change. - Unstable
> users will have a package manager aware of EAPI 6, so all ebuilds
> will be visible for it. - If you mix stable and unstable then you
> are by definition an advanced user, who will be able to cope with
> the situation. :)
>
And, as a developer maintaining bar in #3 above, you should make
sure that either the stable version satisfies all rdeps (even those
in ~arch), or you don't remove the EAPI5 ~arch version until all the
rdeps are EAPI6.
Theoretically repoman could check for this; i don't know if it's
implemented though or if there are any plans to implement it..
IIRC, confirming removals don't break rdeps is not something repoman
can do unless you run a 'repoman full' on the whole tree (or at
least all the rdeps) yourself. This really isn't any different from
the case where foo-1.0 has RDEPEND=" =bar-3.0 " and then bar-3.0 is
dropped.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iF4EAREIAAYFAlZMyF8ACgkQAJxUfCtlWe21RAD7Bxku5bXPbQGLcCwgefjJqadB
LA1tSiK0OkCeUKwvtXEBALw4owHTN/cIOZTFgJkx+scKVvH8lefZbQVjTl9w8KlS
=qb2w
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-11-18 18:50 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
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 [this message]
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=564CC85F.3060400@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