On 8 August 2014 18:21:08 CEST, gottl...@nyu.edu wrote: >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
Perl-cleaner and python-updater ensure the different perl and python dependent parts are rebuild against the configured perl and python packages. Usually these are the latest versions. Problems can occur when you run emerge --depclean and the perl or python versions used for said packages disappear. I also would have concerns if different versions were used for different packages and they need to work together. I always run perlcleaner and python updater after each update. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
