From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: gcc 4.7.3 --> 4.8.3
Date: Mon, 10 Nov 2014 18:52:09 +0000 (UTC) [thread overview]
Message-ID: <loom.20141110T194737-379@post.gmane.org> (raw)
In-Reply-To: 9194407.LW02KBNQ1l@wstn
Peter Humphrey <peter <at> prh.myzen.co.uk> writes:
> > You should be able to just switch to 4.8 without rebuilding anything.
> > That's what I did. Of course it can't hurt to rebuild everything, but
> > you can schedule that for later (like an overnight rebuild of <at> world
> > with --keep-going). It's not critical to do it immediately.
That's exactly what I did, more or less. All seems fine.
> I'd have thought you needed to emerge -e world if you really want to be
> protected.
Yea, maybe. I read the man page on emptytree. I get it actually replaces
by a "reinstall". Does this do more than if I just reboot after
emerge @system @world and then reboot?
I'd be curious to know exactly what reinstall does that is not covered
by just starting up a given code again?
Is it that it forces a reinstall and stop/starts the binary without
rebooting?
Rebooting catches *everything* even better than --emptytree ?
James
next prev parent reply other threads:[~2014-11-10 18:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 17:46 [gentoo-user] gcc 4.7.3 --> 4.8.3 James
2014-11-07 18:19 ` Mark Pariente
2014-11-08 19:08 ` Stefan G. Weichinger
2014-11-08 22:39 ` Volker Armin Hemmann
2014-11-07 19:01 ` Todd Goodman
2014-11-08 16:17 ` [gentoo-user] " Nikos Chantziaras
2014-11-08 19:55 ` James
2014-11-09 9:59 ` Peter Humphrey
2014-11-10 18:52 ` James [this message]
2014-11-10 22:23 ` Neil Bothwick
2014-11-11 6:04 ` Tomas Mozes
2014-11-11 21:12 ` James
2014-11-11 9:51 ` Dale
2014-11-11 20:19 ` James
2014-11-11 21:03 ` Neil Bothwick
2014-11-11 21:27 ` Mick
2014-11-12 2:07 ` James
2014-11-12 10:18 ` Neil Bothwick
2014-11-14 4:52 ` Jonathan Callen
2014-11-14 9:55 ` Neil Bothwick
2014-11-12 5:58 ` 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=loom.20141110T194737-379@post.gmane.org \
--to=wireless@tampabay.rr.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