From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] updating ALL packages
Date: Thu, 24 Jul 2014 23:57:04 +0100 [thread overview]
Message-ID: <20140724235704.557fe0e6@hactar.digimed.co.uk> (raw)
In-Reply-To: <874my82oo3.fsf@nyu.edu>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
On Wed, 23 Jul 2014 09:24:44 -0400, gottlieb@nyu.edu wrote:
> I had mistakenly thought this would update all packages not at the
> latest version (subject to package.accept_keywords, package.mask, ...).
It only updates runtime dependencies, you need --with-bdeps=y to update
all dependencies. However, the default is no for a good reason, there's
no need to update build time deps once the package is installed.
> 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.
>
> As a result eix-test-obsolete finds that I have packages installed that
> are no longer in the database.
That shouldn't happen. If an installed package is removed for the tree,
portage should either install the highest version that matches your
settings or print a warning.
> I could do
>
> emerge --update the-2-dozen-such-packages
>
> Is that wise?
No, as it will add them to world (this behaviour of -u appears to vary
depending on portage version, wind direction and sunspot activity). Use
--oneshot.
--
Neil Bothwick
You can't teach a new mouse old clicks.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-07-24 22:57 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 ` [gentoo-user] " gottlieb
2014-07-24 22:18 ` Michael Orlitzky
2014-07-24 22:57 ` Neil Bothwick [this message]
2014-07-25 1:51 ` [gentoo-user] " 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=20140724235704.557fe0e6@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--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