From: Willie Wong <wwong@princeton.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 'emerge -e world' question
Date: Tue, 13 Jan 2009 11:38:05 -0500 [thread overview]
Message-ID: <20090113163805.GA6686@math.princeton.edu> (raw)
In-Reply-To: <58965d8a0901130820l459f7878k6311f0db3b4f4ae1@mail.gmail.com>
On Tue, Jan 13, 2009 at 10:20:19AM -0600, Paul Hartman wrote:
> >> I normally do "emerge -uDvN @world" (or in other words "emerge
> >> --update --deep --verbose --newuse @world"). Right now, it tells me
> >> this:
<snip>
> > read the man page.
> >
> > Especially the bit about bdeps - these are usually not included
> > in 'emerge -uND world' but will be included when you use -e
<snip>
> When I do "emerge -Dtp openoffice" it shows this:
>
<snip>
> I'm still not entirely clear on why those appear with --deep
> openoffice but not --deep world. If they are build-time deps, wouldn't
> they be included when I emerge openofifce without --deep? If they are
> related to dev-perl/Archive-Zip-1.26 (as it appears), which is
> installed, why don't they get touched by @world? Maybe I just can't
> wrap my brain around how it works, please have patience with me.
> thanks :)
The problem with this last one is not --deep. It is --update.
When you issued emerge --update --deep world, it found that according
to the installed ebuild portage kept, that
a) OpenOffice does not need rebuilding-- since there is no update
according to version number.
b) none of the dependencies installed by openoffice needs
rebuilding, since there is no update.
But when you issued emerge --deep openoffice, you asked for portage to
consider rebuilding openoffice, which now looks at the ebuild in the
tree, which, as you noted, is different from the ebuild that you
emerged months ago. As such, any new dependencies that differs between
the two ebuilds and any build-time dependencies will need to be
satisfied.
And my suggestion would be to just ignore this little thing with
openoffice. If open office runs, and that the ebuild change is minor
enough to not get a new release number, then you can probably wait
until the next release of openoffice to worry about updates.
W
--
Willie W. Wong wwong@math.princeton.edu
408 Fine Hall, Department of Mathematics, Princeton University, Princeton
A mathematician's reputation rests on the number of bad proofs he has given.
next prev parent reply other threads:[~2009-01-13 16:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 15:44 [gentoo-user] 'emerge -e world' question Paul Hartman
2009-01-13 15:47 ` [gentoo-user] " Paul Hartman
2009-01-13 23:55 ` b.n.
2009-01-14 0:05 ` Paul Hartman
2009-01-14 0:18 ` Willie Wong
2009-01-14 0:26 ` »Q«
2009-01-13 15:52 ` [gentoo-user] " Alan McKinnon
2009-01-13 16:02 ` Mike Kazantsev
2009-01-13 16:25 ` Paul Hartman
2009-01-13 16:41 ` Albert Hopkins
2009-01-13 16:20 ` Paul Hartman
2009-01-13 16:37 ` Paul Hartman
2009-01-13 16:38 ` Willie Wong [this message]
2009-01-13 16:57 ` Willie Wong
2009-01-13 17:10 ` Paul Hartman
2009-01-13 17:27 ` Willie Wong
2009-01-13 17:45 ` Paul Hartman
2009-01-13 16:02 ` Albert Hopkins
2009-01-13 20:28 ` Dale
2009-01-13 20:37 ` Paul Hartman
2009-01-13 21:02 ` Dale
2009-01-13 21:18 ` Paul Hartman
2009-01-13 21:20 ` Neil Bothwick
2009-01-13 22:26 ` Dale
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=20090113163805.GA6686@math.princeton.edu \
--to=wwong@princeton.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