From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] world upgrade a mess, need some advise
Date: Wed, 03 Jul 2024 11:52:23 +0100 [thread overview]
Message-ID: <1940216.taCxCBeP46@rogueboard> (raw)
In-Reply-To: <511cff59-e850-c697-524d-b563c0e9bafe@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2541 bytes --]
On Wednesday, 3 July 2024 01:34:12 BST Dale wrote:
> Eli Schwartz wrote:
> > On 7/2/24 7:33 PM, Dale wrote:
> >> What I wish, emerge would spit the information out after it completes
> >> instead of putting fairly important info in some log files somewhere for
> >> a person to go dig and find. It already tells us we should run
> >> --depclean. Why can't it tell us when we need to run some python tool,
> >> perl or anything else as well that has been triggered. I've never seen
> >> emerge tell me to run anything but --depclean or preserved rebuild and
> >> to be honest, if a package isn't used, it likely doesn't hurt anything
> >> that it is still installed. It's just cruft left behind. Having a
> >> broken python, perl or some other important package should give us a
> >> notice at the end. That to me would be more important than running
> >> -depclean. Running preserved rebuild is important tho.
> >>
> >> One thing about it, if it doesn't need to fix anything, I guess it does
> >> nothing. Might upset a few electrons while checking is all. ;-)
> >
> > ... but it already does exactly this?
> >
> > When a package emits a warning in the middle of 50 other packages being
> > compiled and installed... portage collects warnings and repeats them at
> > the end for you.
> >
> > It doesn't matter because the package manager already rebuilds pretty
> > much all perl modules. Running perl-cleaner is advised "in case portage
> > missed something" which probably means "it wasn't part of @world".
>
> All I've ever seen is --depclean and preserved rebuild. I don't recall
> ever seeing anything else. If a package fails, then it tacks the log
> file on the end, sometimes of multiple packages. To be honest tho, if
> it fails, most of the time that isn't useful either. Usually the actual
> error is way up somewhere. I've never seen anything about perl, python
> or that sort of thing before.
>
> It could be that my emerge options are good enough that it doesn't
> trigger any of those. When I had to run perl cleaner a while back tho,
> I wish emerge had gave me a hint that it needed to be run if it couldn't
> fix it itself. Then again, it may not have known about it either.
>
> I plan to run it and if it does nothing, at least then I know my system
> is set up correctly. It's better than not doing it and having weird
> problems that are hard to figure out the cause of.
>
> Dale
>
> :-) :-)
When perl itself is updated emerge let's you know to run perl-cleaner with a
message at the end.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-07-03 10:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 10:04 [gentoo-user] world upgrade a mess, need some advise John Covici
2024-07-01 10:34 ` Michael
2024-07-01 11:23 ` Wols Lists
2024-07-01 13:53 ` Dale
2024-07-01 19:27 ` John Covici
2024-07-01 19:54 ` Dale
2024-07-01 23:16 ` Wol
2024-07-02 3:54 ` John Covici
2024-07-02 8:57 ` Dale
2024-07-02 9:17 ` Arve Barsnes
2024-07-02 12:54 ` Dale
2024-07-02 16:49 ` Wols Lists
2024-07-02 22:04 ` Arve Barsnes
2024-07-02 23:33 ` Dale
2024-07-03 0:20 ` Eli Schwartz
2024-07-03 0:34 ` Dale
2024-07-03 10:52 ` Michael [this message]
2024-07-03 13:24 ` 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=1940216.taCxCBeP46@rogueboard \
--to=confabulate@kintzios.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