Re: [gentoo-user] perl-cleaner lerfovers

[Tanstaafl <tanstaafl@libertytrek.org>]

On 3/2/2015 9:25 AM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Mon, 02 Mar 2015 08:14:41 -0500
> Tanstaafl <tanstaafl@libertytrek.org> wrote:
> 
>> On 2/14/2015 6:37 AM, bitlord <bitlord0xff@gmail.com> wrote:
>>> On Sat, 14 Feb 2015 13:13:25 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?
>>
>>> As I understand this, it is safe to remove and that is what I do
>>> when they appear on my system, if you don't have perl 5.16.3,
>>> 5.18.2 or 5.12.4 ..., and updated/rebuild all perl modules with
>>> perl-cleaner.
>>>
>>> I also used 'qfile /path/to/file' (from portage-utils) to check if
>>> they belong to any installed package. (which is probably not needed,
>>> per-cleaner knows about this?)
>>
>> I'm curious about this...
>>
>> After updating to 5.20, I got a similar message, but a lot more, and
>> strangely, all of which (except the very last one) are in lib32
>> instead of lib64.
>>
>> So, to confirm, it is safe to remove these?
>>
>> If so, then I guess the obvious question is, *if* it really is safe to
>> remove these, why doesn't portage just go ahead and do it
>> automatically?
>>
>> Here is the list of files left over on mine:
>>
>>  * The following files remain. These were either installed by hand
>>  * or edited. This script cannot deal with them.
> 
> ^^^^^^^^^^^^^^^^^^^^
> 
> You missed this bit. The output clearly says that the script cannot
> determine why the files are there or why they are different, therefore
> it will NOT remove them.
> 
> It's not portage giving you that output btw, it's perl-cleaner. It
> works on the basis that it will only clean up files that a) portage
> installed and b) that are still the same as when portage installed
> them. If either case is not true, the script refuses to deal with it
> and tells the human to make a decision.

Oh, right, sorry, too much googling before my second cup of coffee...

> In this specific case, all except two files come from emul-linux 32 bit
> and they are all safe to delete (even the two except ones). But do note
> I know this becuase I've been here before and figured it out, not
> becuase of some magic portage flag.

Thanks Alan...

So... how would one know, for sure, if and when these are safe to
delete? Would that be only if I know for sure that I did not manually
install these myself or put them there (which I haven't and most likely
wouldn't, but would remember if I did)?