public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] conversion of USE=nocxx to USE=cxx
Date: Mon, 14 Nov 2011 15:03:04 -0500	[thread overview]
Message-ID: <201111141503.04898.vapier@gentoo.org> (raw)
In-Reply-To: <4EC16531.3010302@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 1030 bytes --]

On Monday 14 November 2011 14:00:01 Mike Gilbert wrote:
> On 11/13/2011 11:37 PM, Mike Frysinger wrote:
> > On Sunday 13 November 2011 16:42:39 Mike Gilbert wrote:
> >> If I understand you correctly, you are just going to add a "cxx" use
> >> flag to gcc for some transitional period? If so, I can simply switch it
> >> at some point after you add the new flag?
> > 
> > transition period:
> > http://sources.gentoo.org/www-client/google-chrome/google-chrome-17.0.932
> > .0_alpha108826.ebuild?r1=1.1&r2=1.2
> > 
> > eventually you can drop the [-nocxx] dep, but it'll prob be a while.
> 
> Why do I need the [-nocxx] dep at this point? Everybody is going to end
> up rebuilding gcc with the new use flag anyway.

some people might, but not everyone.  if we remove the [-nocxx], and someone 
where to run `emerge google-chrome -u`, portage would fail with dependency 
errors.  i'd leave the dep in there for a while until most people have 
upgraded naturally.  perhaps after the next gcc stabilization.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-11-14 20:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-13 18:42 [gentoo-dev] conversion of USE=nocxx to USE=cxx Mike Frysinger
2011-11-13 21:42 ` Mike Gilbert
2011-11-14  3:49   ` [gentoo-dev] " Ryan Hill
2011-11-14 15:43     ` Mike Gilbert
2011-11-14  4:37   ` [gentoo-dev] " Mike Frysinger
2011-11-14 19:00     ` Mike Gilbert
2011-11-14 20:03       ` Mike Frysinger [this message]
2011-11-14 20:42         ` Mike Gilbert
2011-11-14 17:40 ` Mike Frysinger

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=201111141503.04898.vapier@gentoo.org \
    --to=vapier@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