From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How can I update *every* ebuild?
Date: Thu, 24 Jan 2013 09:21:38 +0200 [thread overview]
Message-ID: <20130124092138.293f757e@khamul.example.com> (raw)
In-Reply-To: <51003E73.2080201@gmail.com>
On Wed, 23 Jan 2013 20:48:03 +0100
Jarry <mr.jarry@gmail.com> wrote:
> Hi Gentoo-users,
> I always thought the right way to update everything was:
>
> emerge --update --deep --newuse world
> emerge --update --deep --newuse system
>
> When I try the above mentioned, nothing to update is found.
> Yet when I try i.e. "emerge --pretend nasm", I see:
>
> [ebuild U ] dev-lang/nasm-2.10.05 [2.10.01]
>
> So there is apparently update for dev-lang/nasm, yet it was
> not pulled when I tried to update the "world" or "system".
> And who knows for how many other ebuilds there is update
> available...
>
> So how can I update really *every* ebuild?
What are your bdep settings in make.conf? (see man emerge for more info
on bdeps)
nasm is unlikely to be a run-time depend for anything, considering
what it does it's more likely to be a build depend. If nothing in world
that uses nasm to build itslef is to be built, then nasm won't be
upgraded; it will be left as-is until it really does need to be
rebuilt.
You should learn to trust portage, it knows more about your system than
you do. "really update every package" sounds a lot more like pedantic
OCD insistence that it all be done always rather than a sensible
decision :-) And before anyone rips me a new one for being
unbelievably rude to list users again, I have the same issue myself. So
I got really good at spotting it and recognizing why it is not really a
good thing.
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2013-01-24 7:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 19:48 [gentoo-user] How can I update *every* ebuild? Jarry
2013-01-23 19:52 ` Florian Philipp
2013-01-23 19:53 ` Michael Mol
2013-01-23 20:07 ` Hilco Wijbenga
2013-01-23 20:24 ` Michael Mol
2013-01-24 0:02 ` Dale
2013-01-23 21:21 ` Bruce Hill
2013-01-23 22:27 ` Neil Bothwick
2013-01-23 23:01 ` Bruce Hill
2013-01-23 23:15 ` Neil Bothwick
2013-01-23 23:37 ` Bruce Hill
2013-01-24 8:32 ` Neil Bothwick
2013-01-24 9:17 ` Dale
2013-01-24 9:27 ` Neil Bothwick
2013-01-24 9:46 ` Dale
2013-01-24 12:37 ` Neil Bothwick
2013-01-24 12:54 ` Jean-Christophe Bach
2013-01-24 13:38 ` Yohan Pereira
2013-01-24 14:04 ` Neil Bothwick
2013-01-24 12:43 ` Kerin Millar
2013-01-24 14:12 ` Trevor D. Manning
2013-01-24 18:17 ` [gentoo-user] " »Q«
2013-01-24 7:21 ` Alan McKinnon [this message]
2013-01-24 12:59 ` [gentoo-user] " Kerin Millar
2013-01-24 15:41 ` Stroller
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=20130124092138.293f757e@khamul.example.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