From: Daniel Campbell <zlg@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] EAPI 6 portage is out!
Date: Thu, 19 Nov 2015 00:13:11 -0800 [thread overview]
Message-ID: <564D8497.6040300@gentoo.org> (raw)
In-Reply-To: <CAGDaZ_pAPmVWJaMtv1+AAtpYQ_1zNkGw=AO1dJogrZj25s8Wtg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 11/18/2015 01:54 AM, Raymond Jennings wrote:
> On Wed, Nov 18, 2015 at 1:25 AM, Alexander Berntsen
> <bernalex@gentoo.org <mailto:bernalex@gentoo.org>> wrote:
>
> On 18/11/15 08:25, Ulrich Mueller wrote:
>> - If you mix stable and unstable then you are by definition an
>> advanced user, who will be able to cope with the situation. :)
> This attitude is shitty, and I am willing to wager a really big
> bunch of users fall into this category.
>
>
>> I second the motion.
>
>> I can vouch for myself as such a user who often uses unstable
>> packages to get new features or dodge bugs in the stable
>> versions.
>
>> As a general default, though, I stick with stable packages.
>
>> Taking an occasional unstable package in an otherwise stable
>> system (and obeying any revbump directives provoked by
>> dependencies) is a legal operation that is actually supported by
>> commit rules that prohibit stable versions from depending on
>> unstable versions of dependencies.
>
>> Why would that policy exist if mixing stable and unstable were
>> unsupported?
>
Mixing keywords is generally unsupported because of the sheer amount
of testing and possible combinations there are. In many cases, you can
get away with it and it's easy enough to debug, but if you end up in
package.use hell and/or have a bunch of blockers, you're kinda on your
own.
The policy exists to prevent developers from causing users to fall
into the trap of mixing keywords. Stable packages depending on testing
packages means they'll have to add entries to package.accept_keywords,
which can greatly complicate maintenance of a Gentoo system. Someone
willing to do that work *is* advanced, even if it's only a few
packages. "Advanced" doesn't have to mean "can build an LFS system in
an evening". :)
In the case of this recent change, worst case scenario you'll need to
add portage to your p.accept_keywords until it's stable. If you want
to simplify things, choose arch or ~arch without mixing.
In the Gentoo spirit, though, users are free to do with their systems
whatever they want; mixing keywords is one of the cases where you get
to keep the pieces, however.
> I don't think EAPI 6 is *that* shiny, that we need to start using
> it prior to stable Portage supporting it. It's a potential mess for
> a huge portion of our users.
>
>
> That said, I'd like to extend my thanks to Micha? for working on
> this.
>
>
- --
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWTYSSAAoJEAEkDpRQOeFw0w0QANEwsIEHWWmZ0jhHJTGHZY1s
oYogl3uNYQypSchyUait6VBMfTCvQ/mOCVgZMy8iIegKRbpY7tWqFG5GA2nXW0br
FRXhsrC5hg5pFDKRj3cpI2DURXWrFomRs+fKrEbpOvy5EeTEcki8o1+tRb7D2FWj
xGT8hkIbs3i2d1wSBzr2HPJEm7DS0259LrrmcT4EPKp6fuRZzAT3YScSN3f7wFBg
OrFZwtlW4MWQSmHhq0z0MqnG50y6j6xIlECwUCo/zGjVn/7ergd7BXldXb18ix11
BJgqWkslIf4Ys6jSgzcecTTDF6eimi6Owc05PhOHqMdH/iU2uPm7RekmJGRaUWel
jwYutEpnzMR2dyxWlPVWL+O34UFTMKpw/BFwULg6zSBJpbYfwfFvPoWlLSTv/w1m
oikrjXiQArP2Hr7pL/Y+E2z/acFQeKg1oNIFOWac6UEyh35rfCZErdw+zLwGjU7A
RYtXWWzbfHeBu3lNIYWKIpvov0BOySXJ6R/rinxvyfO0ojr1WveOajRgGGgjl7Sq
BfLG0SMhfY5qOXqw2NRARB8UFst96k/aPqPLXYdoOeIr97hx8tPurKFy1DXyHaxM
Jyox5844Fv9hbPaAIxc+S8EppslnExp8G/bM7OuLVdy1/H0iKOt6npI7OcOcMKt/
6rQ4FVxXoxGzayM4yUYq
=83f3
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-11-19 8:13 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 [this message]
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=564D8497.6040300@gentoo.org \
--to=zlg@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