| 1 |
On Sun, Apr 16 2017, Alan McKinnon wrote: |
| 2 |
|
| 3 |
> On 17/04/2017 01:07, allan gottlieb wrote: |
| 4 |
>> Am I correct in believing that when perl-cleaner --all, at the end of a |
| 5 |
>> run, asserts |
| 6 |
>> |
| 7 |
>> * It seems like perl-cleaner had to rebuild some packages. |
| 8 |
>> * |
| 9 |
>> * The following files remain. These were either installed by hand |
| 10 |
>> * or edited. |
| 11 |
>> * /usr/lib64/perl5/vendor_perl/5.22.2/XML/SAX/ParserDetails.ini : |
| 12 |
>> * known, can be deleted |
| 13 |
>> * /usr/lib64/perl5/vendor_perl/5.20.2/XML/SAX/ParserDetails.ini : |
| 14 |
>> * known, can be deleted |
| 15 |
>> |
| 16 |
>> the correct response is to trust it and delete the file? |
| 17 |
> |
| 18 |
> |
| 19 |
> In those specific cases, yes. |
| 20 |
> |
| 21 |
> ParserDetails.ini is one of those perl files that do get modified during |
| 22 |
> the normal operation of the perl code. |
| 23 |
> perl-cleaner is being smart and telling you the file is not the same as |
| 24 |
> when it was installed, so it leaves the deletion up to you. |
| 25 |
> |
| 26 |
> Your current perl is neither 5.20.2 nor 5.22.2, those .ini files will |
| 27 |
> now never be used and so they are safe to delete. |
| 28 |
> |
| 29 |
> Side note: you can't always just delete everything in that section of |
| 30 |
> perl-cleaner output. Often, the script can't tell what it is and the |
| 31 |
> module was not put there by portage, so you must decide what to d on a |
| 32 |
> case by case basis. |
| 33 |
|
| 34 |
Thank you. |
| 35 |
allan |
Archives