From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [OT] How to be a penguin.
Date: Sun, 29 May 2016 04:20:08 -0500 [thread overview]
Message-ID: <574AB448.6080108@gmail.com> (raw)
In-Reply-To: <20160529095815.62ab0895@digimed.co.uk>
Neil Bothwick wrote:
> On Sat, 28 May 2016 20:48:37 -0700, Daniel Frey wrote:
>
>>> Furthermore, the current portage doesn't require the revdep-rebuild
>>> step because
>>> of the @preserved-rebuild set creation.
>> I beg to differ, portage still misses stuff more often than you think. I
>> always run revdep-rebuild after an emerge.
> I have a weekly system health check cron job that includes revdep-rebuild
> -pi (hint to Alan: that's the correct way to have revdep-rebuild ignore
> the results of previous runs). It rarely finds anything. There's still
> the occasional glitch with preserved-libs, but I fons it works
> ninety-lots % of the time, and it is far better than the "let it break
> then try to fix it approach" of the days we needed to rely on
> revdep-rebuild.
>
>
I haven't ran revdep-rebuild in likely over a year. Just for giggles, I
ran it a bit ago. The only thing it found was libreoffice. That's not
exactly a critical package or anything. Given that, I don't think it
really serves any point.
I wonder if me having backtrack set to 100 helps with that? Of course,
unlike poor Alan, I also have a sane approach to upgrading. I also run
the latest non-9999 version of portage.
Dale
:-) :-)
next prev parent reply other threads:[~2016-05-29 9:20 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 16:05 [gentoo-user] How to be a penguin Alan Grimes
2016-05-28 16:19 ` [gentoo-user] Re: [OT] " »Q«
2016-05-28 17:06 ` Dale
2016-05-28 18:05 ` Gregory Woodbury
2016-05-28 18:18 ` Neil Bothwick
2016-05-28 18:22 ` Alec Ten Harmsel
2016-05-28 18:33 ` Dale
2016-05-28 18:49 ` Dale
2016-05-28 19:54 ` Volker Armin Hemmann
2016-05-28 20:10 ` Dale
2016-05-29 18:03 ` »Q«
2016-05-28 20:53 ` Neil Bothwick
2016-05-29 1:17 ` Gregory Woodbury
2016-05-29 3:48 ` Daniel Frey
2016-05-29 8:58 ` Neil Bothwick
2016-05-29 9:20 ` Dale [this message]
2016-05-29 16:25 ` Daniel Frey
2016-05-29 19:33 ` Dale
2016-05-29 12:18 ` Alan Grimes
2016-05-29 8:28 ` Håkon Alstadheim
2016-05-29 9:28 ` Dale
2016-05-29 10:26 ` Alan McKinnon
2016-05-29 10:56 ` Neil Bothwick
2016-05-29 17:54 ` Dale
2016-05-29 20:15 ` Alan McKinnon
2016-05-29 21:27 ` Volker Armin Hemmann
2016-05-31 2:14 ` Dale
2016-05-29 12:13 ` Alan Grimes
2016-05-29 17:50 ` »Q«
2016-05-29 19:40 ` Dale
2016-05-29 17:51 ` Dale
2016-05-31 0:32 ` Alan Grimes
2016-05-31 1:00 ` Volker Armin Hemmann
2016-05-31 2:01 ` Dale
2016-05-31 6:02 ` Alan McKinnon
2016-05-31 7:54 ` Neil Bothwick
2016-05-29 21:13 ` Neil Bothwick
2016-05-31 0:48 ` Alan Grimes
2016-05-31 5:31 ` J. Roeleveld
2016-05-31 7:50 ` Neil Bothwick
2016-05-29 23:58 ` Gregory Woodbury
2016-05-30 6:25 ` R0b0t1
2016-05-31 0:57 ` Alan Grimes
2016-05-31 5:34 ` J. Roeleveld
2016-05-31 13:32 ` Alan Grimes
2016-05-31 14:21 ` James
2016-05-31 18:30 ` R0b0t1
2016-05-31 18:44 ` Alan Grimes
2016-05-30 8:30 ` Peter Humphrey
2016-05-28 20:11 ` ng0
2016-05-28 18:20 ` Neil Bothwick
2016-05-28 18:38 ` Dale
2016-05-29 8:45 ` Peter Humphrey
2016-05-29 8:58 ` Peter Humphrey
2016-05-29 17:25 ` [gentoo-user] " Grant Edwards
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=574AB448.6080108@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