From: Daniel Pielmeier <daniel.pielmeier@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "emerge -pvuND world" versus "emerge -pveuND world"
Date: Wed, 11 Oct 2006 23:33:56 +0200 [thread overview]
Message-ID: <452D6344.3040005@googlemail.com> (raw)
In-Reply-To: <3126779c0610111310m5c051254i75e9293f21b259dd@mail.gmail.com>
> Actually, with the 'emptytree' option, it should be trying to rebuild
> everything in your 'world' set along with the dependancies using their
> current versions and use flags. I'm guessing that the odd behavior is
> because you're using it in conjunction with 'uND'. 'Update' and
> 'newuse' go against part of what 'emptytree' does, and 'emptytree' is
> as 'deep' as it gets. :)
I get the same output with "emerge -pve world", so the statement from
Boris seems more reasonable to me.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-11 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 19:31 [gentoo-user] "emerge -pvuND world" versus "emerge -pveuND world" Daniel Pielmeier
2006-10-11 19:51 ` Boris Fersing
2006-10-11 20:10 ` Trey Gruel
2006-10-11 21:33 ` Daniel Pielmeier [this message]
2006-10-11 22:02 ` Bo Ørsted Andresen
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=452D6344.3040005@googlemail.com \
--to=daniel.pielmeier@googlemail.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