On Fri, Aug 08 2014, Rich Freeman wrote: > On Fri, Aug 8, 2014 at 2:23 AM, J. Roeleveld <jo...@antarean.org> wrote: >> I notice a few perl blockers. >> You could try the following: >> >> # emerge -vuD1 $(qlist -IC 'virtual/perl-*') >> # perl-cleaner --all -v -- -v >> >> And then retry to update world. >> I've been encountering some perl blockages myself, and this cleared >> it up for me. > > On stable the most recent perl update seems very prone to blockers, > and I found that cleaning out the virtuals using the first command > given helped portage sort things out considerably. > > If a package outputs an update notice like that, it is usually for a > reason...
I see. On my other systems, no blockers have been reported. Should I run the two commands above anyway? I do understand "if it ain't broke, don't fix it", but I wonder if there are problems waiting to happen that those two commands would eliminate. thanks, allan
