From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: updating ALL packages
Date: Thu, 24 Jul 2014 18:18:40 -0400 [thread overview]
Message-ID: <53D18640.3070805@gentoo.org> (raw)
In-Reply-To: <87k374yy3t.fsf@nyu.edu>
On 07/23/2014 09:59 AM, gottlieb@nyu.edu wrote:
>
> This must be wrong since my procedure does sometimes offer to update
> non-world packages
...
> 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.
I think all you're missing is the build-time dependencies. If one
package needs another (say, cmake) to build but not to run, then portage
won't update it by default when you update @world. You can change that
behavior by passing --with-bdeps to emerge.
From `man emerge`:
--with-bdeps < y | n >
In dependency calculations, pull in build time dependencies that
are not strictly required. This defaults to ´n´ for installation
actions, meaning they will not be installed, and ´y´ for the
--depclean action, meaning they will not be removed. This set‐
ting can be added to EMERGE_DEFAULT_OPTS (see make.conf(5)) and
later overridden via the command line.
next prev parent reply other threads:[~2014-07-24 22:18 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 [this message]
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=53D18640.3070805@gentoo.org \
--to=mjo@gentoo.org \
--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