Mark Knecht wrote:
On Wed, Sep 14, 2011 at 3:19 PM, Neil Bothwick<n...@digimed.co.uk> wrote:
On Wed, 14 Sep 2011 17:03:34 -0500, Dale wrote:
I agree with the other post about gcc but you should also update
portage shortly after that. The newer portage is able to handle more
issues for you and may save you some time. So, I would update gcc,
portage then give world a try. If it looks bad, try system first.
That could correct some things.
Update portage first, that way you are using the newest version when
updating gcc and glibc.
Personally, I'd trust portage to know better than me and do
emerge -au @system
emerge -auDN @world
--
Neil Bothwick
Not that I know anything about the OP's environment but on my KDE
desktop I've recently (last 6 months or so) found that
emerge -fDuN @system
won't work as it ends up with unresolvable conflicts. May just be the
way I've set up my flags.
I completely agree with the sentiment:
1) Update the system's view of portage
eix-sync
2) emerge portage
3) Do the rest of the work
emerge -fDuN @world
emerge -pvDuN @world
Fix USE flag issues, if any
4) Do the build
emerge -DuN -j13 @world
Cheers,
Mark
A lot of this is going to depend on *what* needs to be updated. I did
want to mention openrc because that requires user input for sure. Me, I
would sync and look at the output of emerge -uvDNa world and just see
how much there is to chew on. If the list is really really long, I
would do a emerge -e world after upgrading gcc and portage. When that
is done, the OP should have a really sane system since everything will
be newly compiled.
Again, that is just me. Over the years I have learned how to avoid some
update issues. The most important thing to watch for tho is openrc.
Miss that and rebooting may only be a dream.
YMMV.
Dale
:-) :-)
