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