public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: »Q« <boxcars@gmx.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: EAPI 6 portage is out!
Date: Wed, 18 Nov 2015 10:47:33 -0600	[thread overview]
Message-ID: <20151118104733.73286126@sepulchrave.remarqs> (raw)
In-Reply-To: 22092.23414.863950.329173@a1i15.kph.uni-mainz.de

On Wed, 18 Nov 2015 12:05:26 +0100
Ulrich Mueller <ulm@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. :)
  
> Only that there is no real difference to the existing situation when
> mixing stable and unstable. It is not guaranteed that all dependencies
> of an unstable package are stable, so already now users may have to
> accept the ~ keyword for dependencies in some cases. Similarly, such
> users may have to accept EAPI 6 for some dependencies, which implies
> that they install a package manager supporting EAPI 6.

When ~ keywording is needed for dependencies, the PM's output makes it
clear what's needed.  In cases where EAPI 6 is needed for dependencies
but the PM is unaware of EAPI 6, will there be good clues in the PM's
output that the PM itself needs to be ~ keyworded?




  parent reply	other threads:[~2015-11-18 16: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             ` »Q« [this message]
2015-11-18 17:06               ` [gentoo-dev] " 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=20151118104733.73286126@sepulchrave.remarqs \
    --to=boxcars@gmx.net \
    --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