public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New profile 17: How urgent is the rebuild of world technically?
Date: Mon, 4 Dec 2017 15:21:10 -0500	[thread overview]
Message-ID: <20021862-02ae-28af-95d4-1807cd89033e@gentoo.org> (raw)
In-Reply-To: <0adadf6c-753a-4d47-e810-1df7fffb826d@xunil.at>

On 12/04/2017 12:48 PM, Stefan G. Weichinger wrote:
> On 12/03/2017 03:30 AM, Michael Orlitzky wrote:
> 
>> However, you can delay switching to the new profile for a while.
> 
> For how long?
> 
> eselect news item tells me:
> 
> "Please migrate away from the 13.0 profiles within the six weeks after
> GCC 6.4.0 has been stabilized on your architecture. The 13.0 profiles
> will be deprecated then and removed in half a year."
> 

Once the profile is deprecated (not yet), you've got six months.

Keep in mind that a profile isn't actually all that complicated. It
consists mainly of a few small text files, and can likely be copied
locally just like you would with an ebuild.

You also aren't required to rebuild everything right now (although you
should, to get the PIE/SSP protection!). You can pause your "emerge -e
@world" at any point, and resume it during off-hours or a slow period.
So long as you don't need to build anything else in the meantime, you
can take as long as you want.


  reply	other threads:[~2017-12-04 20:22 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
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 [this message]
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=20021862-02ae-28af-95d4-1807cd89033e@gentoo.org \
    --to=mjo@gentoo.org \
    --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