[gentoo-user] perl-cleaner lerfovers

[gentoo-user] perl-cleaner lerfovers

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 442 bytes --]

'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?

Thanks.

[-- Attachment #2: Type: text/html, Size: 548 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[bitlord]

On Sat, 14 Feb 2015 13:13:25 +0200
Alexander Kapshuk <alexander.kapshuk@gmail.com> 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?
> 
> Thanks.

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?)

Re: [gentoo-user] perl-cleaner lerfovers

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]

On Sat, Feb 14, 2015 at 1:37 PM, bitlord <bitlord0xff@gmail.com> wrote:

> On Sat, 14 Feb 2015 13:13:25 +0200
> Alexander Kapshuk <alexander.kapshuk@gmail.com> 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?
> >
> > Thanks.
>
> 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?)
>
> Understood. Thanks.

I am running 'dev-lang/perl-5.20.1-r4', so I guess I'll just go ahead and
remove the files left over. They don't seem to belong to any package I
currently have installed. I verified that using qfile and 'equery  b'.

[-- Attachment #2: Type: text/html, Size: 1915 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1715 bytes --]

On Saturday 14 Feb 2015 11:48:57 Alexander Kapshuk wrote:
> On Sat, Feb 14, 2015 at 1:37 PM, bitlord <bitlord0xff@gmail.com> wrote:
> > On Sat, 14 Feb 2015 13:13:25 +0200
> > 
> > Alexander Kapshuk <alexander.kapshuk@gmail.com> 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?
> > > 
> > > Thanks.
> > 
> > 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?)
> > 
> > Understood. Thanks.
> 
> I am running 'dev-lang/perl-5.20.1-r4', so I guess I'll just go ahead and
> remove the files left over. They don't seem to belong to any package I
> currently have installed. I verified that using qfile and 'equery  b'.

I think that you should check your /var/lib/portage/world to make sure that 
you have not inadvertently added any perl packages in there.  Then emerge -C 
any found and after that run @preserved-rebuild to bring in anything required.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]

On Sat, Feb 14, 2015 at 2:12 PM, Mick <michaelkintzios@gmail.com> wrote:

> On Saturday 14 Feb 2015 11:48:57 Alexander Kapshuk wrote:
> > On Sat, Feb 14, 2015 at 1:37 PM, bitlord <bitlord0xff@gmail.com> wrote:
> > > On Sat, 14 Feb 2015 13:13:25 +0200
> > >
> > > Alexander Kapshuk <alexander.kapshuk@gmail.com> 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?
> > > >
> > > > Thanks.
> > >
> > > 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?)
> > >
> > > Understood. Thanks.
> >
> > I am running 'dev-lang/perl-5.20.1-r4', so I guess I'll just go ahead and
> > remove the files left over. They don't seem to belong to any package I
> > currently have installed. I verified that using qfile and 'equery  b'.
>
> I think that you should check your /var/lib/portage/world to make sure that
> you have not inadvertently added any perl packages in there.  Then emerge
> -C
> any found and after that run @preserved-rebuild to bring in anything
> required.
> --
> Regards,
> Mick
>

Thanks. Does this one count?

grep -i perl /var/lib/portage/world
sys-devel/libperl

[-- Attachment #2: Type: text/html, Size: 2852 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2262 bytes --]

On Saturday 14 Feb 2015 12:19:54 Alexander Kapshuk wrote:
> On Sat, Feb 14, 2015 at 2:12 PM, Mick <michaelkintzios@gmail.com> wrote:
> > On Saturday 14 Feb 2015 11:48:57 Alexander Kapshuk wrote:
> > > On Sat, Feb 14, 2015 at 1:37 PM, bitlord <bitlord0xff@gmail.com> wrote:
> > > > On Sat, 14 Feb 2015 13:13:25 +0200
> > > > 
> > > > Alexander Kapshuk <alexander.kapshuk@gmail.com> 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?
> > > > > 
> > > > > Thanks.
> > > > 
> > > > 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?)
> > > > 
> > > > Understood. Thanks.
> > > 
> > > I am running 'dev-lang/perl-5.20.1-r4', so I guess I'll just go ahead
> > > and remove the files left over. They don't seem to belong to any
> > > package I currently have installed. I verified that using qfile and
> > > 'equery  b'.
> > 
> > I think that you should check your /var/lib/portage/world to make sure
> > that you have not inadvertently added any perl packages in there.  Then
> > emerge -C
> > any found and after that run @preserved-rebuild to bring in anything
> > required.
> > --
> > Regards,
> > Mick
> 
> Thanks. Does this one count?
> 
> grep -i perl /var/lib/portage/world
> sys-devel/libperl

Yes, you shouldn't really have any libs in your world file.  Any required 
would be pulled in as dependencies.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 2873 bytes --]

On Sat, Feb 14, 2015 at 2:39 PM, Mick <michaelkintzios@gmail.com> wrote:

> On Saturday 14 Feb 2015 12:19:54 Alexander Kapshuk wrote:
> > On Sat, Feb 14, 2015 at 2:12 PM, Mick <michaelkintzios@gmail.com> wrote:
> > > On Saturday 14 Feb 2015 11:48:57 Alexander Kapshuk wrote:
> > > > On Sat, Feb 14, 2015 at 1:37 PM, bitlord <bitlord0xff@gmail.com>
> wrote:
> > > > > On Sat, 14 Feb 2015 13:13:25 +0200
> > > > >
> > > > > Alexander Kapshuk <alexander.kapshuk@gmail.com> 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?
> > > > > >
> > > > > > Thanks.
> > > > >
> > > > > 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?)
> > > > >
> > > > > Understood. Thanks.
> > > >
> > > > I am running 'dev-lang/perl-5.20.1-r4', so I guess I'll just go ahead
> > > > and remove the files left over. They don't seem to belong to any
> > > > package I currently have installed. I verified that using qfile and
> > > > 'equery  b'.
> > >
> > > I think that you should check your /var/lib/portage/world to make sure
> > > that you have not inadvertently added any perl packages in there.  Then
> > > emerge -C
> > > any found and after that run @preserved-rebuild to bring in anything
> > > required.
> > > --
> > > Regards,
> > > Mick
> >
> > Thanks. Does this one count?
> >
> > grep -i perl /var/lib/portage/world
> > sys-devel/libperl
>
> Yes, you shouldn't really have any libs in your world file.  Any required
> would be pulled in as dependencies.
>
> --
> Regards,
> Mick
>
I didn't know that. Thanks. I seem to have quite a few in my world file at
the moment. I didn't put any of them in there by hand though, to the best
of my knowledge.

grep -i libs /var/lib/portage/world
dev-libs/glib
dev-libs/libevent
dev-libs/libyaml
media-libs/gst-plugins-base
media-libs/gst-plugins-base:0.10
media-libs/gstreamer
media-libs/gstreamer:0.10
media-libs/libpng
media-libs/libpng:1.2
media-libs/libpng:1.5
media-libs/libv4l
media-libs/webrtc-audio-processing
sys-libs/gpm

[-- Attachment #2: Type: text/html, Size: 4211 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[Peter Humphrey]

On Saturday 14 February 2015 14:46:01 Alexander Kapshuk wrote:
> On Sat, Feb 14, 2015 at 2:39 PM, Mick <michaelkintzios@gmail.com> 
wrote:
> > [...] you shouldn't really have any libs in your world file.  Any
> > required would be pulled in as dependencies.
> 
> I didn't know that. Thanks. I seem to have quite a few in my world
> file at the moment. I didn't put any of them in there by hand though,
> to the best of my knowledge.

Don't forget that emerge -u <package> will put the package in your world 
file unless you give it -1 as well.

-- 
Rgds
Peter.

Re: [gentoo-user] perl-cleaner lerfovers

[Walter Dnes]

On Sat, Feb 14, 2015 at 02:46:01PM +0200, Alexander Kapshuk wrote
>
> I didn't know that. Thanks. I seem to have quite a few in my world file at
> the moment. I didn't put any of them in there by hand though, to the best
> of my knowledge.
> 
> grep -i libs /var/lib/portage/world
> dev-libs/glib
> dev-libs/libevent
> dev-libs/libyaml
> media-libs/gst-plugins-base
> media-libs/gst-plugins-base:0.10
> media-libs/gstreamer
> media-libs/gstreamer:0.10
> media-libs/libpng
> media-libs/libpng:1.2
> media-libs/libpng:1.5
> media-libs/libv4l
> media-libs/webrtc-audio-processing
> sys-libs/gpm

  As Peter has noted, you probably updated most of these files manually
without supplying the "-1" (or "--oneshot") option.  I do know that
sys-libs/gpm must be in world if you want a text-console mouse-pointer,
because it's a user-selected install.  I checked on my system.  The
following are on my system, but not in world.

dev-libs/glib
dev-libs/libevent
media-libs/libpng (=media-libs/libpng-1.6.16)

  If you've emerged any package with the "gstreamer" flag, then...

media-libs/gst-plugins-base
media-libs/gst-plugins-base:0.10
media-libs/gstreamer
media-libs/gstreamer:0.10

...don't belong in world.  If you want to clean up world safely, I
suggest the following...

1) make a backup of /var/lib/portage/world

2) edit /var/lib/portage/world, by removing the following lines...

dev-libs/glib
dev-libs/libevent
media-libs/libpng
media-libs/libpng:1.2
media-libs/libpng:1.5
media-libs/gst-plugins-base
media-libs/gst-plugins-base:0.10
media-libs/gstreamer
media-libs/gstreamer:0.10

3) run the command "emerge -p --depclean" and post the output back here
before doing anything more.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] perl-cleaner lerfovers

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 2689 bytes --]

On Mon, Feb 16, 2015 at 12:52 AM, Walter Dnes <waltdnes@waltdnes.org> wrote:

> On Sat, Feb 14, 2015 at 02:46:01PM +0200, Alexander Kapshuk wrote
> >
> > I didn't know that. Thanks. I seem to have quite a few in my world file
> at
> > the moment. I didn't put any of them in there by hand though, to the best
> > of my knowledge.
> >
> > grep -i libs /var/lib/portage/world
> > dev-libs/glib
> > dev-libs/libevent
> > dev-libs/libyaml
> > media-libs/gst-plugins-base
> > media-libs/gst-plugins-base:0.10
> > media-libs/gstreamer
> > media-libs/gstreamer:0.10
> > media-libs/libpng
> > media-libs/libpng:1.2
> > media-libs/libpng:1.5
> > media-libs/libv4l
> > media-libs/webrtc-audio-processing
> > sys-libs/gpm
>
>   As Peter has noted, you probably updated most of these files manually
> without supplying the "-1" (or "--oneshot") option.  I do know that
> sys-libs/gpm must be in world if you want a text-console mouse-pointer,
> because it's a user-selected install.  I checked on my system.  The
> following are on my system, but not in world.
>
> dev-libs/glib
> dev-libs/libevent
> media-libs/libpng (=media-libs/libpng-1.6.16)
>
>   If you've emerged any package with the "gstreamer" flag, then...
>
> media-libs/gst-plugins-base
> media-libs/gst-plugins-base:0.10
> media-libs/gstreamer
> media-libs/gstreamer:0.10
>
> ...don't belong in world.  If you want to clean up world safely, I
> suggest the following...
>
> 1) make a backup of /var/lib/portage/world
>
> 2) edit /var/lib/portage/world, by removing the following lines...
>
> dev-libs/glib
> dev-libs/libevent
> media-libs/libpng
> media-libs/libpng:1.2
> media-libs/libpng:1.5
> media-libs/gst-plugins-base
> media-libs/gst-plugins-base:0.10
> media-libs/gstreamer
> media-libs/gstreamer:0.10
>
> 3) run the command "emerge -p --depclean" and post the output back here
> before doing anything more.
>
> --
> Walter Dnes <waltdnes@waltdnes.org>
> I don't run "desktop environments"; I run useful applications
>
>
Thanks for your reply.

What I've done on two of my gentoo systems is, what had been suggested in
one of the earlier replies to this thread. I ran emerge -C `grep -i libs
/var/lib/portage/world`, followed by emerge @preserved-rebuild.
While on another one of my systems I tried emerge --deselect `grep -i libs
/var/lib/portage/world`, followed by emerge --depclean.

As a result, I no longer have any libs in my world set.

I should probably put sys-libs/gpm back into the world set via emerge
--noreplace, based on what you said about the package.

I should probably look into what does and what doesn't have to go into the
world file. Up until recently I assumed that portage would figure that out
for me.

[-- Attachment #2: Type: text/html, Size: 3770 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 3105 bytes --]

On Monday 16 Feb 2015 16:35:15 Alexander Kapshuk wrote:
> On Mon, Feb 16, 2015 at 12:52 AM, Walter Dnes <waltdnes@waltdnes.org> wrote:
> > On Sat, Feb 14, 2015 at 02:46:01PM +0200, Alexander Kapshuk wrote
> > 
> > > I didn't know that. Thanks. I seem to have quite a few in my world file
> > 
> > at
> > 
> > > the moment. I didn't put any of them in there by hand though, to the
> > > best of my knowledge.
> > > 
> > > grep -i libs /var/lib/portage/world
> > > dev-libs/glib
> > > dev-libs/libevent
> > > dev-libs/libyaml
> > > media-libs/gst-plugins-base
> > > media-libs/gst-plugins-base:0.10
> > > media-libs/gstreamer
> > > media-libs/gstreamer:0.10
> > > media-libs/libpng
> > > media-libs/libpng:1.2
> > > media-libs/libpng:1.5
> > > media-libs/libv4l
> > > media-libs/webrtc-audio-processing
> > > sys-libs/gpm
> > > 
> >   As Peter has noted, you probably updated most of these files manually
> > 
> > without supplying the "-1" (or "--oneshot") option.  I do know that
> > sys-libs/gpm must be in world if you want a text-console mouse-pointer,
> > because it's a user-selected install.  I checked on my system.  The
> > following are on my system, but not in world.
> > 
> > dev-libs/glib
> > dev-libs/libevent
> > media-libs/libpng (=media-libs/libpng-1.6.16)
> > 
> >   If you've emerged any package with the "gstreamer" flag, then...
> > 
> > media-libs/gst-plugins-base
> > media-libs/gst-plugins-base:0.10
> > media-libs/gstreamer
> > media-libs/gstreamer:0.10
> > 
> > ...don't belong in world.  If you want to clean up world safely, I
> > suggest the following...
> > 
> > 1) make a backup of /var/lib/portage/world
> > 
> > 2) edit /var/lib/portage/world, by removing the following lines...
> > 
> > dev-libs/glib
> > dev-libs/libevent
> > media-libs/libpng
> > media-libs/libpng:1.2
> > media-libs/libpng:1.5
> > media-libs/gst-plugins-base
> > media-libs/gst-plugins-base:0.10
> > media-libs/gstreamer
> > media-libs/gstreamer:0.10
> > 
> > 3) run the command "emerge -p --depclean" and post the output back here
> > before doing anything more.
> > 
> > --
> > Walter Dnes <waltdnes@waltdnes.org>
> > I don't run "desktop environments"; I run useful applications
> 
> Thanks for your reply.
> 
> What I've done on two of my gentoo systems is, what had been suggested in
> one of the earlier replies to this thread. I ran emerge -C `grep -i libs
> /var/lib/portage/world`, followed by emerge @preserved-rebuild.
> While on another one of my systems I tried emerge --deselect `grep -i libs
> /var/lib/portage/world`, followed by emerge --depclean.
> 
> As a result, I no longer have any libs in my world set.
> 
> I should probably put sys-libs/gpm back into the world set via emerge
> --noreplace, based on what you said about the package.
> 
> I should probably look into what does and what doesn't have to go into the
> world file. Up until recently I assumed that portage would figure that out
> for me.

It does/should.  Until you run regenworld, or emerge -u <package>.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

On Mon, 16 Feb 2015 18:35:15 +0200, Alexander Kapshuk wrote:

> What I've done on two of my gentoo systems is, what had been suggested
> in one of the earlier replies to this thread. I ran emerge -C `grep -i
> libs /var/lib/portage/world`, followed by emerge @preserved-rebuild.

That could have been dangerous, unmerging important libs just because
they have found their way into @world.

> While on another one of my systems I tried emerge --deselect `grep -i
> libs /var/lib/portage/world`, followed by emerge --depclean.

That is far more sensible.
 
> As a result, I no longer have any libs in my world set.

Or you could have done

sed -i /libs\//d /var/lib/portage/world
emerge -ca


-- 
Neil Bothwick

All things being equal, fat people use more soap.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

On Feb 16, 2015 11:26 PM, "Neil Bothwick" <neil@digimed.co.uk> wrote:
>
> On Mon, 16 Feb 2015 18:35:15 +0200, Alexander Kapshuk wrote:
>
> > What I've done on two of my gentoo systems is, what had been suggested
> > in one of the earlier replies to this thread. I ran emerge -C `grep -i
> > libs /var/lib/portage/world`, followed by emerge @preserved-rebuild.
>
> That could have been dangerous, unmerging important libs just because
> they have found their way into @world.
>
> > While on another one of my systems I tried emerge --deselect `grep -i
> > libs /var/lib/portage/world`, followed by emerge --depclean.
>
> That is far more sensible.
>
> > As a result, I no longer have any libs in my world set.
>
> Or you could have done
>
> sed -i /libs\//d /var/lib/portage/world
> emerge -ca
>
>
> --
> Neil Bothwick
>
> All things being equal, fat people use more soap.

Thanks a lot for your feedback. I'm learning as I go.

[-- Attachment #2: Type: text/html, Size: 1241 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[Tanstaafl]

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.

/usr/lib32/perl5/5.16.3/i686-linux/auto/File/Glob/Glob.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Storable/Storable.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Filter/Util/Call/Call.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/DB_File/DB_File.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/GDBM_File/GDBM_File.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Sys/Hostname/Hostname.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Sys/Syslog/Syslog.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Fcntl/Fcntl.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Opcode/Opcode.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/POSIX/POSIX.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Text/Soundex/Soundex.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Time/Piece/Piece.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Time/HiRes/HiRes.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/re/re.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Compress/Raw/Bzip2/Bzip2.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Compress/Raw/Zlib/Zlib.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Socket/Socket.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/List/Util/Util.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/threads/shared/shared.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/threads/threads.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Digest/SHA/SHA.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Digest/MD5/MD5.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/NDBM_File/NDBM_File.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/IO/IO.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Math/BigInt/FastCalc/FastCalc.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Data/Dumper/Dumper.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/IPC/SysV/SysV.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Cwd/Cwd.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/I18N/Langinfo/Langinfo.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/mro/mro.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/PerlIO/scalar/scalar.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/PerlIO/via/via.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/PerlIO/mmap/mmap.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/PerlIO/encoding/encoding.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/CN/CN.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/JP/JP.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/Byte/Byte.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/Symbol/Symbol.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/Encode.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/KR/KR.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/EBCDIC/EBCDIC.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/Unicode/Unicode.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/TW/TW.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Devel/PPPort/PPPort.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Devel/Peek/Peek.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Hash/Util/Util.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Hash/Util/FieldHash/FieldHash.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/arybase/arybase.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/B/B.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Unicode/Normalize/Normalize.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Unicode/Collate/Collate.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/MIME/Base64/Base64.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/SDBM_File/SDBM_File.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/Tie/Hash/NamedCapture/NamedCapture.so
/usr/lib32/perl5/5.16.3/i686-linux/auto/attributes/attributes.so
/usr/lib32/perl5/5.16.3/i686-linux/CORE/perlsfio.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/utfebcdic.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/hv.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/utf8.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/mydtrace.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/regnodes.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/form.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/l1_char_class_tab.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/perlapi.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/thread.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/fakethr.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/pp.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/uconfig.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/EXTERN.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/XSUB.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/sv.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/keywords.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/INTERN.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/dosish.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/charclass_invlists.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/perl.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/opnames.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/mg_raw.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/time64.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/op.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/regexp.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/util.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/opcode.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/perliol.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/nostdio.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/intrpvar.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/pad.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/reentr.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/fakesdio.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/metaconfig.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/uudmap.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/config.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/regcharclass.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/embed.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/embedvar.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/pp_proto.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/mg_data.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/perlsdio.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/scope.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/feature.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/perlvars.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/op_reg_common.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/proto.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/overload.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/av.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/handy.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/perlio.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/patchlevel.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/perly.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/bitcount.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/cop.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/malloc_ctl.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/time64_config.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/patchlevel-gentoo.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/regcomp.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/cv.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/warnings.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/mg.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/mg_vtable.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/unixish.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/iperlsys.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/git_version.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/parser.h
/usr/lib32/perl5/5.16.3/i686-linux/CORE/gv.h
/usr/lib32/perl5/5.16.3/Encode/encode.h
/usr/lib64/perl5/5.12.4/x86_64-linux/Encode/ConfigLocal.pm

Re: [gentoo-user] perl-cleaner lerfovers

[Alan McKinnon]

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.


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.

Alan


> 
> /usr/lib32/perl5/5.16.3/i686-linux/auto/File/Glob/Glob.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Storable/Storable.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Filter/Util/Call/Call.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/DB_File/DB_File.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/GDBM_File/GDBM_File.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Sys/Hostname/Hostname.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Sys/Syslog/Syslog.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Fcntl/Fcntl.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Opcode/Opcode.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/POSIX/POSIX.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Text/Soundex/Soundex.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Time/Piece/Piece.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Time/HiRes/HiRes.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/re/re.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Compress/Raw/Bzip2/Bzip2.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Compress/Raw/Zlib/Zlib.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Socket/Socket.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/List/Util/Util.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/threads/shared/shared.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/threads/threads.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Digest/SHA/SHA.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Digest/MD5/MD5.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/NDBM_File/NDBM_File.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/IO/IO.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Math/BigInt/FastCalc/FastCalc.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Data/Dumper/Dumper.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/IPC/SysV/SysV.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Cwd/Cwd.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/I18N/Langinfo/Langinfo.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/mro/mro.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/PerlIO/scalar/scalar.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/PerlIO/via/via.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/PerlIO/mmap/mmap.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/PerlIO/encoding/encoding.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/CN/CN.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/JP/JP.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/Byte/Byte.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/Symbol/Symbol.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/Encode.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/KR/KR.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/EBCDIC/EBCDIC.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/Unicode/Unicode.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Encode/TW/TW.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Devel/PPPort/PPPort.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Devel/Peek/Peek.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Hash/Util/Util.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Hash/Util/FieldHash/FieldHash.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/arybase/arybase.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/B/B.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Unicode/Normalize/Normalize.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Unicode/Collate/Collate.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/MIME/Base64/Base64.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/SDBM_File/SDBM_File.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/Tie/Hash/NamedCapture/NamedCapture.so
> /usr/lib32/perl5/5.16.3/i686-linux/auto/attributes/attributes.so
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/perlsfio.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/utfebcdic.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/hv.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/utf8.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/mydtrace.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/regnodes.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/form.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/l1_char_class_tab.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/perlapi.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/thread.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/fakethr.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/pp.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/uconfig.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/EXTERN.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/XSUB.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/sv.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/keywords.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/INTERN.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/dosish.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/charclass_invlists.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/perl.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/opnames.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/mg_raw.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/time64.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/op.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/regexp.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/util.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/opcode.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/perliol.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/nostdio.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/intrpvar.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/pad.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/reentr.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/fakesdio.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/metaconfig.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/uudmap.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/config.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/regcharclass.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/embed.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/embedvar.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/pp_proto.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/mg_data.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/perlsdio.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/scope.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/feature.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/perlvars.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/op_reg_common.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/proto.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/overload.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/av.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/handy.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/perlio.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/patchlevel.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/perly.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/bitcount.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/cop.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/malloc_ctl.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/time64_config.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/patchlevel-gentoo.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/regcomp.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/cv.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/warnings.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/mg.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/mg_vtable.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/unixish.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/iperlsys.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/git_version.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/parser.h
> /usr/lib32/perl5/5.16.3/i686-linux/CORE/gv.h
> /usr/lib32/perl5/5.16.3/Encode/encode.h
> /usr/lib64/perl5/5.12.4/x86_64-linux/Encode/ConfigLocal.pm
> 
> 

Re: [gentoo-user] perl-cleaner lerfovers

[Tanstaafl]

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)?

Re: [gentoo-user] perl-cleaner lerfovers

[Alan McKinnon]

On Mon, 02 Mar 2015 09:26:34 -0500
Tanstaafl <tanstaafl@libertytrek.org> wrote:

> > 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)?


I don't have a recipe for this or even a rule of thumb. I usually know
what the files are for (or can Google it) and decide on each case
individually.

For perl-cleaner output, the perl version of the old install is in the
pathname, so I check if the corresponding file for the new perl version
is already installed, that tells me the old one is safe to delete. On a
64bit system, I know the 32bit files come from emul-linux, so I can
delete those too on the same basis.

For everything else from perl-cleaner, I have to figure out why I
changed the file myself and make sure the same change is present in the
new version.

It gets more complicated if you use cpan (stuff can get changed behind
the scenes). So the best approach is always to understand what the
various tools do and deal with it on that basis.

Alan

Re: [gentoo-user] perl-cleaner lerfovers

[Alan McKinnon]

On 14/02/2015 13:13, 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?


That happens when something other than portage created of changed the
listed files.

Installing stuff from CPAN will do it, I get it a lot with -emul
packages. Anything that even touches the files will trigger that warning.

To fully deal with them:

1. Check you have neither perl-5.16.3 or perl-5.18.2 installed. If so,
those 3 artifacts will never be used by anything
2. Check that you have xml-sax and encode installed for your latest
installed perl.
3. Delete the stuff perl-cleaner is moaning about




#2 is the important one


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] perl-cleaner lerfovers

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]

On Sat, Feb 14, 2015 at 5:24 PM, Alan McKinnon <alan.mckinnon@gmail.com>
wrote:

> On 14/02/2015 13:13, 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?
>
>
> That happens when something other than portage created of changed the
> listed files.
>
> Installing stuff from CPAN will do it, I get it a lot with -emul
> packages. Anything that even touches the files will trigger that warning.
>
> To fully deal with them:
>
> 1. Check you have neither perl-5.16.3 or perl-5.18.2 installed. If so,
> those 3 artifacts will never be used by anything
> 2. Check that you have xml-sax and encode installed for your latest
> installed perl.
> 3. Delete the stuff perl-cleaner is moaning about
>
>
>
>
> #2 is the important one
>
>
> --
> Alan McKinnon
> alan.mckinnon@gmail.com
>
>
>
Understood. Thanks.

equery -q l dev-lang/perl
dev-lang/perl-5.20.1-r4

equery -q l '*XML-SAX*'
dev-perl/XML-SAX-0.990.0-r1
dev-perl/XML-SAX-Base-1.80.0-r1

equery -q l '*[Ee]ncode*'
dev-perl/Encode-Locale-1.30.0-r1
virtual/perl-Encode-2.600.0

I take it it is safe to remove the perl files left over.

[-- Attachment #2: Type: text/html, Size: 2290 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[Alan McKinnon]

On 14/02/2015 17:42, Alexander Kapshuk wrote:
> On Sat, Feb 14, 2015 at 5:24 PM, Alan McKinnon <alan.mckinnon@gmail.com
> <mailto:alan.mckinnon@gmail.com>> wrote:
> 
>     On 14/02/2015 13:13, 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?
> 
> 
>     That happens when something other than portage created of changed the
>     listed files.
> 
>     Installing stuff from CPAN will do it, I get it a lot with -emul
>     packages. Anything that even touches the files will trigger that
>     warning.
> 
>     To fully deal with them:
> 
>     1. Check you have neither perl-5.16.3 or perl-5.18.2 installed. If so,
>     those 3 artifacts will never be used by anything
>     2. Check that you have xml-sax and encode installed for your latest
>     installed perl.
>     3. Delete the stuff perl-cleaner is moaning about
> 
> 
> 
> 
>     #2 is the important one
> 
> 
>     --
>     Alan McKinnon
>     alan.mckinnon@gmail.com <mailto:alan.mckinnon@gmail.com>
> 
> 
> 
> Understood. Thanks.
> 
> equery -q l dev-lang/perl
> dev-lang/perl-5.20.1-r4
> 
> equery -q l '*XML-SAX*'
> dev-perl/XML-SAX-0.990.0-r1
> dev-perl/XML-SAX-Base-1.80.0-r1
> 
> equery -q l '*[Ee]ncode*'
> dev-perl/Encode-Locale-1.30.0-r1
> virtual/perl-Encode-2.600.0
> 
> I take it it is safe to remove the perl files left over.
> 


Yes



-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] perl-cleaner lerfovers

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 2076 bytes --]

On Sat, Feb 14, 2015 at 6:04 PM, Alan McKinnon <alan.mckinnon@gmail.com>
wrote:

> On 14/02/2015 17:42, Alexander Kapshuk wrote:
> > On Sat, Feb 14, 2015 at 5:24 PM, Alan McKinnon <alan.mckinnon@gmail.com
> > <mailto:alan.mckinnon@gmail.com>> wrote:
> >
> >     On 14/02/2015 13:13, 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?
> >
> >
> >     That happens when something other than portage created of changed the
> >     listed files.
> >
> >     Installing stuff from CPAN will do it, I get it a lot with -emul
> >     packages. Anything that even touches the files will trigger that
> >     warning.
> >
> >     To fully deal with them:
> >
> >     1. Check you have neither perl-5.16.3 or perl-5.18.2 installed. If
> so,
> >     those 3 artifacts will never be used by anything
> >     2. Check that you have xml-sax and encode installed for your latest
> >     installed perl.
> >     3. Delete the stuff perl-cleaner is moaning about
> >
> >
> >
> >
> >     #2 is the important one
> >
> >
> >     --
> >     Alan McKinnon
> >     alan.mckinnon@gmail.com <mailto:alan.mckinnon@gmail.com>
> >
> >
> >
> > Understood. Thanks.
> >
> > equery -q l dev-lang/perl
> > dev-lang/perl-5.20.1-r4
> >
> > equery -q l '*XML-SAX*'
> > dev-perl/XML-SAX-0.990.0-r1
> > dev-perl/XML-SAX-Base-1.80.0-r1
> >
> > equery -q l '*[Ee]ncode*'
> > dev-perl/Encode-Locale-1.30.0-r1
> > virtual/perl-Encode-2.600.0
> >
> > I take it it is safe to remove the perl files left over.
> >
>
>
> Yes
>
>
>
> --
> Alan McKinnon
> alan.mckinnon@gmail.com
>
>
> Thanks a lot.

[-- Attachment #2: Type: text/html, Size: 3302 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[Andreas K. Huettel]

[-- Attachment #1: Type: Text/Plain, Size: 805 bytes --]

Am Samstag, 14. Februar 2015, 12:13:25 schrieb Alexander Kapshuk:
> '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?
> 
> Thanks.

They are safe to remove.

category "I'll do it when I get around to it."
https://bugs.gentoo.org/show_bug.cgi?id=509096

-- 
Andreas K. Huettel
Gentoo Linux developer (council, perl, libreoffice)
dilfridge@gentoo.org
http://www.akhuettel.de/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [gentoo-user] perl-cleaner lerfovers

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 928 bytes --]

On Sat, Feb 14, 2015 at 7:08 PM, Andreas K. Huettel <dilfridge@gentoo.org>
wrote:

> Am Samstag, 14. Februar 2015, 12:13:25 schrieb Alexander Kapshuk:
> > '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?
> >
> > Thanks.
>
> They are safe to remove.
>
> category "I'll do it when I get around to it."
> https://bugs.gentoo.org/show_bug.cgi?id=509096
>
> --
> Andreas K. Huettel
> Gentoo Linux developer (council, perl, libreoffice)
> dilfridge@gentoo.org
> http://www.akhuettel.de/
>

Understood. Thanks.

[-- Attachment #2: Type: text/html, Size: 1672 bytes --]

Re: [gentoo-user] perl-cleaner leftovers

[Thanasis]

Shouldn't all participating in this thread have corrected by now the 
message's subject, for archiving purposes?

Re: [gentoo-user] perl-cleaner leftovers

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 235 bytes --]

On Sat, Feb 14, 2015 at 9:19 PM, Thanasis <thanasis@asyr.hopto.org> wrote:

> Shouldn't all participating in this thread have corrected by now the
> message's subject, for archiving purposes?
>
> Thanks for spotting and correcting it.

[-- Attachment #2: Type: text/html, Size: 545 bytes --]