public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gcc-4.8 may be needed in stable for www-client/chromium-38.x
Date: Sun, 17 Aug 2014 18:32:04 +0200	[thread overview]
Message-ID: <53F0D904.2020306@gentoo.org> (raw)
In-Reply-To: <20140729184957.4feafbb3@pomiot.lan>

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

On 7/29/14 6:49 PM, Michał Górny wrote:
> Dnia 2014-07-23, o godz. 19:48:17
> ""Paweł Hajdan, Jr."" <phajdan.jr@gentoo.org> napisał(a):
> 
>> Looks like www-client/chromium is going to start using c++11 seriously
>> and require gcc-4.8+, see thread
>> <https://groups.google.com/a/chromium.org/d/msg/chromium-packagers/fvJvPG8fa7I/iWPEsUxhKikJ>
>>
>> This is in the dev channel for now, but given the 6 weeks release cycle
>> it'll go to stable in about 3 months, and every time it's a security update.
>>
>> I'm trying to get Gentoo prepared now, and so what are our chances to
>> get gcc-4.8 to stable by that time?
> 
> For the record: https://bugs.gentoo.org/show_bug.cgi?id=516152
> 
> I think 4.8 should be our current choice for stable since 4.7 is
> unsupported upstream and 4.7.4 (4.7.3 is stable now) has known unfixed
> bugs.

Sounds good, should we set a specific version as a stabilization target?

I'm successfully using 4.8.3 here.

Paweł



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 841 bytes --]

      reply	other threads:[~2014-08-17 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 17:48 [gentoo-dev] gcc-4.8 may be needed in stable for www-client/chromium-38.x "Paweł Hajdan, Jr."
2014-07-29 16:28 ` Mike Gilbert
2014-07-29 16:39   ` Georg Rudoy
2014-07-29 16:49 ` Michał Górny
2014-08-17 16:32   ` "Paweł Hajdan, Jr." [this message]

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=53F0D904.2020306@gentoo.org \
    --to=phajdan.jr@gentoo.org \
    --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