From: tuxic@posteo.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New profile 17: How urgent is the rebuild of world technically?
Date: Sun, 3 Dec 2017 04:26:55 +0100 [thread overview]
Message-ID: <20171203032655.tg6xodvlb3i5xpm3@solfire> (raw)
In-Reply-To: <73314087-5fa1-d75f-8a2e-a74857026f9c@gentoo.org>
On 12/02 09:30, Michael Orlitzky wrote:
> On 12/02/2017 09:15 PM, tuxic@posteo.de wrote:
> > Hi,
> >
> > the instruction of the news item about the swicth to profile 17 says
> > that one needs to rebuild @world.
> >
> > Is this technically needed?
>
> Yes, unless you were already using a hardened toolchain.
>
>
> > Would it be possible to do this on base of the daily updates intead
> > all in one go?
>
> No, you'll get build failures trying to link new packages against old
> libraries.
>
> However, you can delay switching to the new profile for a while.
>
Delaying would not solve the problem as it is...
If the compilation will fail at a certain point (and it will fail,
since this is a complete new thing) -- would it be possible to resume
even some tweaks, hacks and patches (even certain recompilations)
would be needed in between?
Can I stop a running emerge @world and resume later?
How does a restarted emerge @world recognizes packages, which are
already compiled according to the new standard?
Cheers
Meino
next prev parent reply other threads:[~2017-12-03 3:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 2:15 [gentoo-user] New profile 17: How urgent is the rebuild of world technically? tuxic
2017-12-03 2:30 ` Michael Orlitzky
2017-12-03 2:32 ` Adam Carter
2017-12-03 2:44 ` Michael Orlitzky
2017-12-03 3:26 ` tuxic [this message]
2017-12-03 3:35 ` Heiko Baums
2017-12-03 3:45 ` tuxic
2017-12-03 4:15 ` Heiko Baums
2017-12-03 9:53 ` Peter Humphrey
2017-12-03 11:56 ` Heiko Baums
2017-12-03 12:55 ` Dale
2017-12-03 14:09 ` Spackman, Chris
2017-12-03 14:16 ` tuxic
2017-12-03 14:39 ` Heiko Baums
2017-12-03 15:25 ` Peter Humphrey
2017-12-03 15:57 ` Neil Bothwick
2017-12-03 14:36 ` Heiko Baums
2017-12-03 14:27 ` Heiko Baums
2017-12-04 1:08 ` Dale
2017-12-04 1:18 ` Heiko Baums
2017-12-04 1:48 ` Walter Dnes
2017-12-03 5:26 ` Adam Carter
2017-12-03 10:51 ` Neil Bothwick
2017-12-03 3:47 ` Heiko Baums
2017-12-06 23:59 ` Frank Steinmetzger
2017-12-07 8:08 ` Neil Bothwick
2017-12-04 17:48 ` Stefan G. Weichinger
2017-12-04 20:21 ` Michael Orlitzky
2017-12-05 9:16 ` Stefan G. Weichinger
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=20171203032655.tg6xodvlb3i5xpm3@solfire \
--to=tuxic@posteo.de \
--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