From: "Gregory M. Turner" <gmt@be-evil.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] impending c++11 clusterfuck?
Date: Mon, 30 Nov 2015 01:18:53 -0800 [thread overview]
Message-ID: <2013565.JLJVQGAH25@moneypit> (raw)
In-Reply-To: <20151130074235.5a0fec7b.mgorny@gentoo.org>
On Sun, Nov 29, 2015 at 10:42 PM, Michał Górny <mgorny@gentoo.org> wrote:
> On Sun, 29 Nov 2015 19:56:04 -0800
> "Gregory M. Turner" <gmt@be-evil.net> wrote:
> > the mess gets magically cleaned up by robots somehow.
>
> Sadly := can't help here since gcc switches occur independently of
> package installs. And AFAIK revdep-rebuild doesn't help either.
Indeed... magical hand-wavey part is the only teeny-tiny flaw with my
proposal that the problem be magically, hand-wavically solved --
otherwise, it's rock-solid :)
OTOH when you're spending ten hours a week waiting for revdep-rebuild,
preserved-rebuild stops seeming like an intractable fantasy and more
like an interesting puzzle you'd might as well take a crack at
solving.
I dunno about y'all but my not-really-that-computationally-powerful
workstation has 2000 packages installed, about three-quarters of which
seem to have forked webkit (just kidding, but it sure feels that way).
emerge -e @world literally takes me two days if I'm lucky. If I'm
not, more like a week, with my cores left mostly idling while my
productivity is thwarted by various non-webkit-compiling distractions
like using the toilet or working.
Point being, it's damn slow; I'm starting to feel like the guy waiting
for revdep-rebuild all week. There's gotta be a way to do it. If it
requires some encapsulation-breaking hacks to get it done (as
preserved-rebuild kinda did) it's probably well worth it.
-gmt
Greg Turner
gmt@be-evil.net
next prev parent reply other threads:[~2015-11-30 9:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 3:56 [gentoo-dev] impending c++11 clusterfuck? Gregory M. Turner
2015-11-30 4:10 ` C Bergström
2015-11-30 8:52 ` Mikhail Korolev
2015-11-30 6:42 ` Michał Górny
2015-11-30 8:07 ` Anthony G. Basile
2015-11-30 9:52 ` Michał Górny
2015-11-30 11:17 ` Anthony G. Basile
2015-11-30 11:31 ` Anthony G. Basile
2015-11-30 18:34 ` Greg Turner
2015-11-30 18:37 ` Greg Turner
2015-11-30 22:49 ` C Bergström
2015-12-01 8:59 ` Benda Xu
2015-12-01 9:03 ` Anthony G. Basile
2015-12-01 11:25 ` Michał Górny
2015-12-01 12:18 ` Anthony G. Basile
2015-12-02 2:12 ` Gregory M. Turner
2015-12-02 7:06 ` Michał Górny
2015-12-02 7:38 ` Anthony G. Basile
2015-12-02 12:54 ` Patrick Lauer
2015-12-02 10:00 ` Gregory M. Turner
2015-12-02 12:57 ` Michał Górny
2015-11-30 10:16 ` Greg Turner
2015-11-30 10:42 ` Greg Turner
2015-11-30 9:18 ` Gregory M. Turner [this message]
2015-11-30 9:58 ` Michał Górny
2015-11-30 16:48 ` Steven Lembark
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=2013565.JLJVQGAH25@moneypit \
--to=gmt@be-evil.net \
--cc=gentoo-dev@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