From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge - Tips and Tricks
Date: Mon, 2 Sep 2024 02:19:37 -0500 [thread overview]
Message-ID: <e7271d43-7359-809a-d83e-26d95ebcb9d9@gmail.com> (raw)
In-Reply-To: <e7c303d7-5f31-4527-89b1-7e33c0a003a2@youngman.org.uk>
Wols Lists wrote:
> On 02/09/2024 00:56, Dale wrote:
>> Obviously, a news item can change that process. If there is a news item
>> with a different process, follow that for sure. Following the news item
>> to the letter is the best way. The devs work out all the kinks and bugs
>> before they post the news item.
>
> Find the other commands (like perl-cleaner) that you really ought to
> run but are not part of emerge - CPAN predates even linux I believe,
> so they expect us to adjust to them ...
>
> I followed the Python update to the letter, and it just refused to run
> ... until I ran perl-cleaner.
>
> perl-cleaner is basically "emerge for perl" - it goes through and
> sorts out all your CPAN dependencies.
>
> Cheers,
> Wol
This is true. I always forget to run perl update and python tools as
well. I rarely have issues but it is likely a good idea to run it when
one of those are updated, just to be safe.
Joe, add that to your list. ;-)
Dale
:-) :-)
next prev parent reply other threads:[~2024-09-02 7:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 22:44 [gentoo-user] emerge - Tips and Tricks Joe
2024-09-01 23:56 ` Dale
2024-09-02 1:59 ` Joe
2024-09-02 5:11 ` Dale
2024-09-02 6:59 ` Wols Lists
2024-09-02 8:06 ` Michael
2024-09-02 9:17 ` [gentoo-user] " Nuno Silva
2024-09-02 3:53 ` [gentoo-user] " Matt Connell
2024-09-02 5:13 ` Dale
2024-09-02 6:55 ` Wols Lists
2024-09-02 7:19 ` Dale [this message]
2024-09-02 15:11 ` ralfconn
2024-09-03 7:49 ` Dale
2024-09-03 9:05 ` Arve Barsnes
2024-09-03 9:05 ` Arve Barsnes
2024-09-03 10:32 ` Dale
2024-09-02 15:10 ` ralfconn
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=e7271d43-7359-809a-d83e-26d95ebcb9d9@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