From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Update to news item 2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt
Date: Sun, 4 Jun 2017 12:11:20 -0400 [thread overview]
Message-ID: <CAJ0EP42_3oSxpfPu5tOyM9ApXxjXg4z+8sXBUJ7VF80xYaHxHA@mail.gmail.com> (raw)
In-Reply-To: <9c39a81c-c4ed-569c-b168-b5eea02b08d5@gentoo.org>
On Sun, Jun 4, 2017 at 11:55 AM, Anthony G. Basile <blueness@gentoo.org> wrote:
> Hi everyone,
>
> Kensington suggested updating the news item on the new c++11 abi for
> gcc. Since this news item now appears for all new installations of gcc
> it can be annoying. I'm proposing to change it as below, but I have one
> concern. It is important for anyone upgrading from gcc-4 to gcc-5. But
> if an upgrade to gcc-5 removes gcc-4, then the message won't show up
> while it is still relevant.
>
> Any suggestions on how to proceed?
Nit: You probably want <sys-devel/gcc-5, not <=sys-devel/gcc-5.
Portage will flag the news item as relevant as soon as it sees gcc-4*
installed. If a future depclean removes that version, I believe
portage will still display the news item. Even if it doesn't, the user
would still have had to ignore the news item and run the depclean
first.
next prev parent reply other threads:[~2017-06-04 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 15:55 [gentoo-dev] Update to news item 2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt Anthony G. Basile
2017-06-04 16:11 ` Mike Gilbert [this message]
2017-06-04 18:25 ` M. J. Everitt
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=CAJ0EP42_3oSxpfPu5tOyM9ApXxjXg4z+8sXBUJ7VF80xYaHxHA@mail.gmail.com \
--to=floppym@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