public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: rdalek1967@gmail.com
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Official way to do rolling update (Was: Re: Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec)
Date: Mon, 4 Nov 2013 21:27:51 +0100	[thread overview]
Message-ID: <20131104212751.5dea464d@TOMWIJ-GENTOO> (raw)
In-Reply-To: <5277FD54.9020105@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]

On Mon, 04 Nov 2013 14:02:28 -0600
Dale <rdalek1967@gmail.com> wrote:

> You are right, it does require prior knowledge and as a user gets that
> knowledge, they likely end up where Alan, Duncan and myself are.  That
> would be emerge -uaDN world.

And from there you can continue; like adding -vt --unordered-display
and the list goes onto get a lot more detail, it can be handy to see
what depends on what such that you don't look at a flat list wondering
where a dependency came from. I haven't looked further at all the more
specific parameters one can pass; but well, surely there's some
objective and/or subjective improvement still possible there.

> I have needed this more than once in the past.  I would run into a
> problem and recompiling the obvious packages didn't correct the
> issue. Doing a emerge -e world would fix the issue.

Usually I debug / troubleshoot it for long enough to avoid that; but
well, yeah, depending on the situation `emerge -e @world` could take
a lot less time. Especially on a new Gentoo install where this might be
more likely to happen as you often change things in the early days...

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2013-11-04 20:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04  4:15 Official way to do rolling update (Was: Re: [gentoo-dev] Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec) yac
2013-11-04  8:50 ` Daniel Campbell
2013-11-04  9:51   ` [gentoo-dev] Re: Official way to do rolling update (Was: " Duncan
2013-11-04 10:26     ` yac
2013-11-04 12:06       ` Dale
2013-11-04 12:28         ` Tom Wijsman
2013-11-04 15:50           ` Rich Freeman
2013-11-04 20:02           ` Dale
2013-11-04 20:27             ` Tom Wijsman [this message]
2013-11-04 21:47               ` Dale
2013-11-04 23:28           ` Alan McKinnon
2013-11-04 12:12       ` Tom Wijsman
2013-11-04 22:28       ` Duncan
2013-11-04 11:17     ` Martin Vaeth
2013-11-04 21:46       ` Duncan
2013-11-05  1:23         ` Michael Orlitzky
2013-11-05  7:51           ` Duncan
2013-11-05 16:21         ` Daniel Campbell
2013-11-04 21:53     ` Peter Stuge
2013-11-04 11:07 ` Official way to do rolling update (Was: Re: [gentoo-dev] " Tom Wijsman

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=20131104212751.5dea464d@TOMWIJ-GENTOO \
    --to=tomwij@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=rdalek1967@gmail.com \
    /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