Re: [gentoo-user] trusting perl-cleaner

2017-04-17 Thread Andreas K. Huettel
Am Montag, 17. April 2017, 01:09:44 CEST schrieb Alan McKinnon:
> On 17/04/2017 01:07, allan gottlieb wrote:
> > Am I correct in believing that when perl-cleaner --all, at the end of a
> > run, asserts
> > 
> >* It seems like perl-cleaner had to rebuild some packages.
> >*
> >* The following files remain. These were either installed by hand
> >* or edited.
> >* /usr/lib64/perl5/vendor_perl/5.22.2/XML/SAX/ParserDetails.ini  :
> >* known, can be deleted
> >* /usr/lib64/perl5/vendor_perl/5.20.2/XML/SAX/ParserDetails.ini  :
> >* known, can be deleted
> > 
> > the correct response is to trust it and delete the file?
> 
> In those specific cases, yes.

Yes. (OK, I'm biased, I wrote the whitelist. :)
https://github.com/gentoo-perl/perl-cleaner/blob/master/perl-cleaner#L27

> 
> ParserDetails.ini is one of those perl files that do get modified during
> the normal operation of the perl code.
> perl-cleaner is being smart and telling you the file is not the same as
> when it was installed, so it leaves the deletion up to you.

Actually it is created during operation... otherwise it would have been 
removed automatically.

> Your current perl is neither 5.20.2 nor 5.22.2, those .ini files will
> now never be used and so they are safe to delete.

Correct. Essentially, if you have Perl 5.24, everything in directories with 
*other* 5.xx (xx != 24) will be completely ignored. 

[This is NOT true for minor upgrades. Perl 5.24.1 will (in our Gentoo 
configuration) happily use modules in 5.24.0 directories.]

> Side note: you can't always just delete everything in that section of
> perl-cleaner output. Often, the script can't tell what it is and the
> module was not put there by portage, so you must decide what to d on a
> case by case basis.

True, but as of the newest version perl-cleaner has a list of "know stuff that 
should be safe to remove". 

And an option --delete-leftovers for the brave. :)

-- 
Andreas K. Hüttel
dilfri...@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] trusting perl-cleaner

2017-04-16 Thread allan gottlieb
On Sun, Apr 16 2017, Alan McKinnon wrote:

> On 17/04/2017 01:07, allan gottlieb wrote:
>> Am I correct in believing that when perl-cleaner --all, at the end of a
>> run, asserts
>> 
>>* It seems like perl-cleaner had to rebuild some packages.
>>* 
>>* The following files remain. These were either installed by hand
>>* or edited.
>>* /usr/lib64/perl5/vendor_perl/5.22.2/XML/SAX/ParserDetails.ini  :
>>* known, can be deleted
>>* /usr/lib64/perl5/vendor_perl/5.20.2/XML/SAX/ParserDetails.ini  :
>>* known, can be deleted
>> 
>> the correct response is to trust it and delete the file?
>
>
> In those specific cases, yes.
>
> ParserDetails.ini is one of those perl files that do get modified during
> the normal operation of the perl code.
> perl-cleaner is being smart and telling you the file is not the same as
> when it was installed, so it leaves the deletion up to you.
>
> Your current perl is neither 5.20.2 nor 5.22.2, those .ini files will
> now never be used and so they are safe to delete.
>
> Side note: you can't always just delete everything in that section of
> perl-cleaner output. Often, the script can't tell what it is and the
> module was not put there by portage, so you must decide what to d on a
> case by case basis.

Thank you.
allan



Re: [gentoo-user] trusting perl-cleaner

2017-04-16 Thread Alan McKinnon
On 17/04/2017 01:07, allan gottlieb wrote:
> Am I correct in believing that when perl-cleaner --all, at the end of a
> run, asserts
> 
>* It seems like perl-cleaner had to rebuild some packages.
>* 
>* The following files remain. These were either installed by hand
>* or edited.
>* /usr/lib64/perl5/vendor_perl/5.22.2/XML/SAX/ParserDetails.ini  :
>* known, can be deleted
>* /usr/lib64/perl5/vendor_perl/5.20.2/XML/SAX/ParserDetails.ini  :
>* known, can be deleted
> 
> the correct response is to trust it and delete the file?


In those specific cases, yes.

ParserDetails.ini is one of those perl files that do get modified during
the normal operation of the perl code.
perl-cleaner is being smart and telling you the file is not the same as
when it was installed, so it leaves the deletion up to you.

Your current perl is neither 5.20.2 nor 5.22.2, those .ini files will
now never be used and so they are safe to delete.

Side note: you can't always just delete everything in that section of
perl-cleaner output. Often, the script can't tell what it is and the
module was not put there by portage, so you must decide what to d on a
case by case basis.


-- 
Alan McKinnon
alan.mckin...@gmail.com




[gentoo-user] trusting perl-cleaner

2017-04-16 Thread allan gottlieb
Am I correct in believing that when perl-cleaner --all, at the end of a
run, asserts

   * It seems like perl-cleaner had to rebuild some packages.
   * 
   * The following files remain. These were either installed by hand
   * or edited.
   * /usr/lib64/perl5/vendor_perl/5.22.2/XML/SAX/ParserDetails.ini  :
   * known, can be deleted
   * /usr/lib64/perl5/vendor_perl/5.20.2/XML/SAX/ParserDetails.ini  :
   * known, can be deleted

the correct response is to trust it and delete the file?

thanks,
allan