public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Teresa and Dale <teendale@vista-express.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage 2.1 weirdness
Date: Sun, 11 Jun 2006 15:31:13 -0500	[thread overview]
Message-ID: <448C7D91.6070100@vista-express.com> (raw)
In-Reply-To: <358eca8f0606111310r673db732r27c4813ce83a133f@mail.gmail.com>

Mick wrote:

> On 11/06/06, Kristian Poul Herkild <kristian@herkild.dk> wrote:
>
>> Hmm... after having updated to portage 2.1 which has become stable, I
>> get this weird output from emerge and revdep-rebuild:
>
> [snip . . . ]
>
>> Recompiling that much (especially OpenOffice) just because of an update
>> to Portage seems quite excessive to me.
>
>
> As I understand it (I'm sure this has been covered in GWN, forums,
> etc.) USE flags which had been set  automatically by certain packages
> are no longer valid universally.  Therefore, either add those USE
> flags missing (e.g. ldap & mozilla for OOo) in your /etc/make.conf, or
> if you only want them for a particular package add them in
> /etc/portage/package.use.
>
> HTH


Well, I noticed that when I ran revdep-rebuild -p mine wanted to
reemerge gcc too, so I let it.  Then I went back and ran revdep-rebuild
again and it still wants to reemerge gcc.  I did the next thing I could
think of and did a emerge -e system.  When I ran revdep-rebuild -p again
afterwards, it wanted to reemerge gcc again.

Same as the OP, why does it want to go in circles reemerging gcc??  :-/

Dale
:-) :-)
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-06-11 20:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-11 19:25 [gentoo-user] Portage 2.1 weirdness Kristian Poul Herkild
2006-06-11 20:10 ` Mick
2006-06-11 20:31   ` Teresa and Dale [this message]
2006-06-11 21:48     ` Kristian Poul Herkild
2006-06-11 23:49     ` Richard Fish
2006-06-11 20:32   ` Kristian Poul Herkild
2006-06-15 19:55   ` Sergio Polini
2006-06-15 20:27     ` Rumen Yotov
2006-06-15 22:12       ` Mick
2006-06-15 22:46     ` Bo Ørsted Andresen
2006-06-16  6:22       ` Sergio Polini
2006-06-11 22:10 ` b.n.

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=448C7D91.6070100@vista-express.com \
    --to=teendale@vista-express.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