From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gcc-6.x status inquiry
Date: Thu, 4 May 2017 16:20:57 -0500 [thread overview]
Message-ID: <20170504212057.GA5885@whubbs1.gaikai.biz> (raw)
In-Reply-To: <20170503164311.GA20929@whubbs1.gaikai.biz>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
On Wed, May 03, 2017 at 11:43:11AM -0500, William Hubbs wrote:
> Hey all,
>
> I am asking about this because I have been asked to look into
> packaging software that has a specific requirement for >=gcc-6 in order
> to build [1].
>
> I see that gcc-6.3 doesn't have keywords, so I'm
> wondering when it will get them? Does anyone have any idea? I'm not
> talking about stable keywords, just ~. ;-)
After the discussion on this thread (no one seemed to object), I went
ahead just now and added ~ keywords to sys-devel/gcc-6.3.0.
Thanks,
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-05-04 21:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 16:43 [gentoo-dev] gcc-6.x status inquiry William Hubbs
2017-05-03 17:10 ` Hanno Böck
2017-05-03 17:58 ` [gentoo-dev] " Luca Barbato
2017-05-03 18:00 ` Ian Stakenvicius
2017-05-03 18:42 ` William Hubbs
2017-05-03 19:06 ` Ian Stakenvicius
2017-05-03 18:44 ` Erik Närström
2017-05-04 7:28 ` grozin
2017-05-04 7:48 ` Erik Närström
2017-05-03 18:57 ` [gentoo-dev] " Andreas K. Huettel
2017-05-03 19:25 ` Matthias Maier
2017-05-04 15:22 ` Thomas Deutschmann
2017-05-04 21:32 ` Getting gcc-6 keyworded (was: Re: [gentoo-dev] gcc-6.x status inquiry) Andreas K. Huettel
2017-05-04 21:33 ` Andreas K. Huettel
2017-05-04 21:20 ` William Hubbs [this message]
2017-05-04 21:30 ` [gentoo-dev] gcc-6.x status inquiry Matthias Maier
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=20170504212057.GA5885@whubbs1.gaikai.biz \
--to=williamh@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