From: gottlieb@nyu.edu
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: updating ALL packages
Date: Wed, 23 Jul 2014 09:59:50 -0400 [thread overview]
Message-ID: <87k374yy3t.fsf@nyu.edu> (raw)
In-Reply-To: <874my82oo3.fsf@nyu.edu> (gottlieb@nyu.edu's message of "Wed, 23 Jul 2014 09:24:44 -0400")
On Wed, Jul 23 2014, gottlieb@nyu.edu wrote:
> My normal updating procedure is
>
> EMERGE_DEFAULT_OPTS="--ask --deep --tree --verbose --jobs --load-average=5"
> emerge --update --changed-use --keep-going @world
>
> I had mistakenly thought this would update all packages not at the
> latest version (subject to package.accept_keywords, package.mask, ...).
>
> I now realize that it only does this for the packages in world and then
> follows the dependency tree. So if package A in world is up to date, A
> depends of B, and a new version of B appears, B will not be updated.
This must be wrong since my procedure does sometimes offer to update
non-world packages
> As a result eix-test-obsolete finds that I have packages installed that
> are no longer in the database.
>
> I could do
>
> emerge --update the-2-dozen-such-packages
>
> Is that wise?
I would still want to know if the executing the last emerge command is
wise and also would like to understand what my update world procedure
is actually doing.
> thanks,
> allan
PS Sorry for the error. New rule no email to gentoo-user before my
morning shower.
next prev parent reply other threads:[~2014-07-24 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 13:24 [gentoo-user] updating ALL packages gottlieb
2014-07-23 13:59 ` gottlieb [this message]
2014-07-24 22:18 ` [gentoo-user] " Michael Orlitzky
2014-07-24 22:57 ` [gentoo-user] " Neil Bothwick
2014-07-25 1:51 ` gottlieb
2014-07-25 4:13 ` Alan McKinnon
2014-07-25 14:42 ` gottlieb
2014-07-25 4:07 ` Alan McKinnon
2014-07-25 14:43 ` gottlieb
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=87k374yy3t.fsf@nyu.edu \
--to=gottlieb@nyu.edu \
--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