On Sat, Feb 14, 2015 at 6:04 PM, Alan McKinnon <alan.mckin...@gmail.com>
wrote:

> On 14/02/2015 17:42, Alexander Kapshuk wrote:
> > On Sat, Feb 14, 2015 at 5:24 PM, Alan McKinnon <alan.mckin...@gmail.com
> > <mailto:alan.mckin...@gmail.com>> wrote:
> >
> >     On 14/02/2015 13:13, Alexander Kapshuk wrote:
> >     > 'perl-cleaner --all' generated the following output.
> >     >
> >     >  * Finding left over modules and header
> >     >
> >     >  * The following files remain. These were either installed by hand
> >     >  * or edited. This script cannot deal with them.
> >     >
> >     > /usr/lib/perl5/vendor_perl/5.16.3/XML/SAX/ParserDetails.ini
> >     > /usr/lib/perl5/vendor_perl/5.18.2/XML/SAX/ParserDetails.ini
> >     > /usr/lib/perl5/5.12.4/i686-linux/Encode/ConfigLocal.pm
> >     >
> >     > What's the recommended way to go about this?
> >
> >
> >     That happens when something other than portage created of changed the
> >     listed files.
> >
> >     Installing stuff from CPAN will do it, I get it a lot with -emul
> >     packages. Anything that even touches the files will trigger that
> >     warning.
> >
> >     To fully deal with them:
> >
> >     1. Check you have neither perl-5.16.3 or perl-5.18.2 installed. If
> so,
> >     those 3 artifacts will never be used by anything
> >     2. Check that you have xml-sax and encode installed for your latest
> >     installed perl.
> >     3. Delete the stuff perl-cleaner is moaning about
> >
> >
> >
> >
> >     #2 is the important one
> >
> >
> >     --
> >     Alan McKinnon
> >     alan.mckin...@gmail.com <mailto:alan.mckin...@gmail.com>
> >
> >
> >
> > Understood. Thanks.
> >
> > equery -q l dev-lang/perl
> > dev-lang/perl-5.20.1-r4
> >
> > equery -q l '*XML-SAX*'
> > dev-perl/XML-SAX-0.990.0-r1
> > dev-perl/XML-SAX-Base-1.80.0-r1
> >
> > equery -q l '*[Ee]ncode*'
> > dev-perl/Encode-Locale-1.30.0-r1
> > virtual/perl-Encode-2.600.0
> >
> > I take it it is safe to remove the perl files left over.
> >
>
>
> Yes
>
>
>
> --
> Alan McKinnon
> alan.mckin...@gmail.com
>
>
> Thanks a lot.

Reply via email to