From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] cruft after perl-cleaner --all
Date: Sat, 23 Oct 2010 18:30:38 -0500 [thread overview]
Message-ID: <4CC3701E.4010108@gmail.com> (raw)
In-Reply-To: <yu98w1o4t1b.fsf@nyu.edu>
Allan Gottlieb wrote:
> Daniel Pielmeier<billie@gentoo.org> writes:
>
>
>> Allan Gottlieb schrieb am 23.10.2010 18:13:
>>
>>> perl-cleaner could not deal with
>>>
>>> /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX/ParserDetails.ini
>>> /usr/lib/perl5/5.8.8/i686-linux/Encode/ConfigLocal.pm
>>>
>>> I ran
>>> equery belongs
>>> and neither turned up.
>>>
>>>
>> It is cruft! Some leftovers from perl-5.8.8. There should be new ones in
>> the corresponding locations for perl-5.12.2 after upgrading and running
>> perl-cleaner.
>>
> Indeed there were.
>
>
>> /usr/lib/perl5/vendor_perl/5.12.2/XML/SAX/ParserDetails.ini
>> /usr/lib/perl5/5.12.2/i686-linux/Encode/ConfigLocal.pm
>>
>> After the switch to a new perl version and successful run of
>> perl-cleaner it should be safe to remove everything below /usr/lib/perl5
>> /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl for older perl
>> installations, except stuff belonging to packages which were not
>> installed by the package manager or have been altered manually.
>>
> Thank you
> allan
>
>
Yep. I had one file left over that it printed out to. I ran equery b
file/name to see if it belonged to anything and it didn't. A little rm
did the trick.
Is there a way to find "cruft"? Some script or something? My install
is pretty old and I would guess there are a few left over files here and
there.
Dale
:-) :-)
next prev parent reply other threads:[~2010-10-23 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 16:13 [gentoo-user] cruft after perl-cleaner --all Allan Gottlieb
2010-10-23 17:25 ` Daniel Pielmeier
2010-10-23 19:18 ` Allan Gottlieb
2010-10-23 23:30 ` Dale [this message]
2010-10-24 15:38 ` Neil Bothwick
2010-10-24 17:41 ` Dale
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=4CC3701E.4010108@gmail.com \
--to=rdalek1967@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