public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Portage getting slicker?
Date: Thu, 14 Jul 2016 08:17:19 +0200	[thread overview]
Message-ID: <4bb0cd17-633d-81dc-028f-29e947589be7@gmail.com> (raw)
In-Reply-To: <loom.20160714T035906-577@post.gmane.org>

On 14/07/2016 04:03, James wrote:
>> It's unsurprising you got different behaviour
> true, but the -u was in both and a complete different set of 
> packages was considered, by portage, and only one was able to 
> move forward (note the -p was not in the second entry, despite
> my not including that detail).

without -N or -t, portage considers just the list of packages on the
command line.

-N is newuse, portage also considers packages whose USE has changed.
-t is emptytree, portage also considers the entire tree and -u tells it
to not remerge things that don't need updating.

The input set for those commands differs, so the output set might also
be different. Those two commands you ran are not guaranteed to produce
the same results (although the often will).


-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2016-07-14  6:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 18:25 [gentoo-user] Portage getting slicker? James
2016-07-13 21:08 ` Alan McKinnon
2016-07-13 21:41   ` [gentoo-user] " James
2016-07-13 22:53     ` Alan McKinnon
2016-07-14  2:03       ` James
2016-07-14  6:17         ` Alan McKinnon [this message]
2016-07-14  7:52           ` Marc Joliet
2016-07-14 11:43             ` Gevisz
2016-07-14 13:13               ` Franz Fellner
2016-07-14 14:58                 ` James
2016-07-14 21:02               ` Marc Joliet
2016-07-14 20:58     ` Fernando Rodriguez

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=4bb0cd17-633d-81dc-028f-29e947589be7@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@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