Neil Bothwick wrote:
On Thu, 24 Jun 2010 07:46:59 -0500, Dale wrote:
What does emerge --update --newuse --deep --tree --with-bdeps y
@world
actually say?
I'm not sure this is correct but I have to ask this. Since gcc is a
system package, it wouldn't try to upgrade gcc even if one was
available would it? I guess if something in world just had to have
that or a newer version then it would pull the newer gcc in but
otherwise it would skip it right?
@world includes @system. But the problem is not that emerge world is
skipping it but that it wants to downgrade gcc:4.4.
From my understanding, world includes @system but @world does not. I
know here on my rig, I run emerge -uvDNa world and it updates everything
installed including deps and the system packages. If I run @world, it
skips the system packages. At least that is the last time I tried it
which was not to long ago.
One reason I remember this is because of the discussion I had with the
devs on -dev. That is why @system is in /var/lib/portage/world_sets. I
noticed a few weeks ago that there are a couple others added to it as
well. The devs did it that way so that when folks like me upgrade the
old fashioned way and just use world instead of @system and @world.
Has this changed?
Dale
:-) :-)
