From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] perl-cleaner lerfovers
Date: Sat, 14 Feb 2015 18:04:11 +0200 [thread overview]
Message-ID: <54DF71FB.2040009@gmail.com> (raw)
In-Reply-To: <CAJ1xhMWv48UHssu+Z+g-Acy0F9SdHGWkc0fJEDNo_8ORqUd_sg@mail.gmail.com>
On 14/02/2015 17:42, Alexander Kapshuk wrote:
> On Sat, Feb 14, 2015 at 5:24 PM, Alan McKinnon <alan.mckinnon@gmail.com
> <mailto:alan.mckinnon@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.mckinnon@gmail.com <mailto:alan.mckinnon@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.mckinnon@gmail.com
next prev parent reply other threads:[~2015-02-14 16:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 11:13 [gentoo-user] perl-cleaner lerfovers Alexander Kapshuk
2015-02-14 11:37 ` bitlord
2015-02-14 11:48 ` Alexander Kapshuk
2015-02-14 12:12 ` Mick
2015-02-14 12:19 ` Alexander Kapshuk
2015-02-14 12:39 ` Mick
2015-02-14 12:46 ` Alexander Kapshuk
2015-02-14 14:06 ` Peter Humphrey
2015-02-15 22:52 ` Walter Dnes
2015-02-16 16:35 ` Alexander Kapshuk
2015-02-16 16:40 ` Mick
2015-02-16 21:25 ` Neil Bothwick
2015-02-17 16:15 ` Alexander Kapshuk
2015-03-02 13:14 ` Tanstaafl
2015-03-02 14:25 ` Alan McKinnon
2015-03-02 14:26 ` Tanstaafl
2015-03-02 15:22 ` Alan McKinnon
2015-02-14 15:24 ` Alan McKinnon
2015-02-14 15:42 ` Alexander Kapshuk
2015-02-14 16:04 ` Alan McKinnon [this message]
2015-02-14 16:09 ` Alexander Kapshuk
2015-02-14 17:08 ` Andreas K. Huettel
2015-02-14 17:16 ` Alexander Kapshuk
2015-02-14 19:19 ` [gentoo-user] perl-cleaner leftovers Thanasis
2015-02-14 20:07 ` Alexander Kapshuk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54DF71FB.2040009@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox