public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] perl-cleaner --reallyall and leftover files, that I didn't touch.
Date: Mon, 10 Feb 2025 11:11:43 -0600	[thread overview]
Message-ID: <13a960f8-d96e-c7c7-f478-a411a5f9ca73@gmail.com> (raw)
In-Reply-To: <6023620.MhkbZ0Pkbq@rogueboard>

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

Michael wrote:
> On Monday 10 February 2025 10:53:26 Greenwich Mean Time Dale wrote:
>
>> This is the perl I have installed. 
>>
>>
>> dev-lang/perl-5.40.0-r1:0/5.40
>>
>>
>> I'm not going to list all the stuff it spit out.  Just going to include
>> enough that you get the idea. 
>>
>>
>>  *     /usr/lib64/perl5/5.40/Parse/CPAN/Meta.pm
>>  *     /usr/lib64/perl5/5.40/Config/Perl/V.pm
>>  *     /usr/lib64/perl5/5.40/Config/Extensions.pm
>> ...
> These look legit files installed by portage for your perl 5.40 slot.  The 
> message I received after perl-cleaner finished its job was:
> =========================================
> * GNU info directory index is up-to-date.
>  *
>  * 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.40/x86_64-linux/auto/Regexp/
> IPv6/.packlist
>  *     /usr/lib64/perl5/vendor_perl/5.40/x86_64-linux/auto/File/Temp/.packlist
>  *     /usr/lib64/perl5/vendor_perl/5.40/x86_64-linux/auto/File/
> Which/.packlist
>  *     /usr/lib64/perl5/vendor_perl/5.40/x86_64-linux/auto/File/
> chdir/.packlist
> [snip ...]
> ===============
>
> They are all listed under /usr/lib64/perl5/.  Say you want to check if these 
> are really orphaned files no longer owned by any installed package, you can 
> run:
>
> ~ $ qfile -o $(find /usr/lib /usr/lib64 -name "*.packlist")
> ~ $ 
> ~ $ qfile -o $(find /usr/lib /usr/lib64 -name "*.pm")
> ~ $ 
> ~ $ qfile -o $(find /usr/lib /usr/lib64 -name "*.pod")
> ~ $ 
> ~ $ qfile -o $(find /usr/lib /usr/lib64 -name "*.pl")
> ~ $ 
>
> and so on.  In my example above I did not discover any orphans.
>
>
>> They appear to be for the current installed versions.  That's one reason
>> it is kinda confusing.  o_O
> I see what you mean, the message "... These were either installed by hand or 
> edited" can be confusing, because all these perl5 files were installed by 
> portage and perl was invariably brought in as a dependency by some other 
> @system or @world package.


I ran the ones above just to get a general idea.  I got this. 


root@Gentoo-1 / # qfile -o $(find /usr/lib /usr/lib64 -name "*.packlist")
root@Gentoo-1 / # qfile -o $(find /usr/lib /usr/lib64 -name "*.pm")
root@Gentoo-1 / # qfile -o $(find /usr/lib /usr/lib64 -name "*.pod")
root@Gentoo-1 / # qfile -o $(find /usr/lib /usr/lib64 -name "*.pl")
root@Gentoo-1 / #


I ran equery b for some random ones before I posted the original
thread.  It shows they belong to installed packages, perl mostly.  So,
really, they are not orphans is my thinking.  I think it is more likely
that something is confused.  Something got out of sync or something. 
One thing I know for sure, I didn't install any of them by hand nor did
I edit any of them. 

If they really do belong to packages, what is the best way to force
emerge to be aware of it?  I've already re-emerged it so that doesn't
seem to do the job.  I thought about emerge -ek world but doubt that
would help any either. 

Any ideas? 

Dale

:-)  :-) 

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

  reply	other threads:[~2025-02-10 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-09 23:46 [gentoo-user] perl-cleaner --reallyall and leftover files, that I didn't touch Dale
2025-02-10 10:01 ` Michael
2025-02-10 10:53   ` Dale
2025-02-10 11:15     ` Michael
2025-02-10 17:11       ` Dale [this message]
2025-02-17 15:21         ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13a960f8-d96e-c7c7-f478-a411a5f9ca73@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox