| 1 |
On 3/2/2015 9:25 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 |
> On Mon, 02 Mar 2015 08:14:41 -0500 |
| 3 |
> Tanstaafl <tanstaafl@×××××××××××.org> wrote: |
| 4 |
> |
| 5 |
>> On 2/14/2015 6:37 AM, bitlord <bitlord0xff@×××××.com> wrote: |
| 6 |
>>> On Sat, 14 Feb 2015 13:13:25 Alexander Kapshuk wrote: |
| 7 |
>>>> 'perl-cleaner --all' generated the following output. |
| 8 |
>>>> |
| 9 |
>>>> * Finding left over modules and header |
| 10 |
>>>> |
| 11 |
>>>> * The following files remain. These were either installed by hand |
| 12 |
>>>> * or edited. This script cannot deal with them. |
| 13 |
>>>> |
| 14 |
>>>> /usr/lib/perl5/vendor_perl/5.16.3/XML/SAX/ParserDetails.ini |
| 15 |
>>>> /usr/lib/perl5/vendor_perl/5.18.2/XML/SAX/ParserDetails.ini |
| 16 |
>>>> /usr/lib/perl5/5.12.4/i686-linux/Encode/ConfigLocal.pm |
| 17 |
>>>> |
| 18 |
>>>> What's the recommended way to go about this? |
| 19 |
>> |
| 20 |
>>> As I understand this, it is safe to remove and that is what I do |
| 21 |
>>> when they appear on my system, if you don't have perl 5.16.3, |
| 22 |
>>> 5.18.2 or 5.12.4 ..., and updated/rebuild all perl modules with |
| 23 |
>>> perl-cleaner. |
| 24 |
>>> |
| 25 |
>>> I also used 'qfile /path/to/file' (from portage-utils) to check if |
| 26 |
>>> they belong to any installed package. (which is probably not needed, |
| 27 |
>>> per-cleaner knows about this?) |
| 28 |
>> |
| 29 |
>> I'm curious about this... |
| 30 |
>> |
| 31 |
>> After updating to 5.20, I got a similar message, but a lot more, and |
| 32 |
>> strangely, all of which (except the very last one) are in lib32 |
| 33 |
>> instead of lib64. |
| 34 |
>> |
| 35 |
>> So, to confirm, it is safe to remove these? |
| 36 |
>> |
| 37 |
>> If so, then I guess the obvious question is, *if* it really is safe to |
| 38 |
>> remove these, why doesn't portage just go ahead and do it |
| 39 |
>> automatically? |
| 40 |
>> |
| 41 |
>> Here is the list of files left over on mine: |
| 42 |
>> |
| 43 |
>> * The following files remain. These were either installed by hand |
| 44 |
>> * or edited. This script cannot deal with them. |
| 45 |
> |
| 46 |
> ^^^^^^^^^^^^^^^^^^^^ |
| 47 |
> |
| 48 |
> You missed this bit. The output clearly says that the script cannot |
| 49 |
> determine why the files are there or why they are different, therefore |
| 50 |
> it will NOT remove them. |
| 51 |
> |
| 52 |
> It's not portage giving you that output btw, it's perl-cleaner. It |
| 53 |
> works on the basis that it will only clean up files that a) portage |
| 54 |
> installed and b) that are still the same as when portage installed |
| 55 |
> them. If either case is not true, the script refuses to deal with it |
| 56 |
> and tells the human to make a decision. |
| 57 |
|
| 58 |
Oh, right, sorry, too much googling before my second cup of coffee... |
| 59 |
|
| 60 |
> In this specific case, all except two files come from emul-linux 32 bit |
| 61 |
> and they are all safe to delete (even the two except ones). But do note |
| 62 |
> I know this becuase I've been here before and figured it out, not |
| 63 |
> becuase of some magic portage flag. |
| 64 |
|
| 65 |
Thanks Alan... |
| 66 |
|
| 67 |
So... how would one know, for sure, if and when these are safe to |
| 68 |
delete? Would that be only if I know for sure that I did not manually |
| 69 |
install these myself or put them there (which I haven't and most likely |
| 70 |
wouldn't, but would remember if I did)? |
Archives