* [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
@ 2017-06-04 15:55 Anthony G. Basile
2017-06-04 16:11 ` Mike Gilbert
2017-06-04 18:25 ` M. J. Everitt
0 siblings, 2 replies; 3+ messages in thread
From: Anthony G. Basile @ 2017-06-04 15:55 UTC (permalink / raw
To: Gentoo Development
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?
index d074dbe..25f1712 100644
---
a/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt
+++
b/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt
@@ -2,9 +2,9 @@ Title: GCC 4.7 Introduced the New C++11 ABI
Author: Anthony G. Basile <blueness@gentoo.org>
Content-Type: text/plain
Posted: 2014-10-26
-Revision: 1
+Revision: 2
News-Item-Format: 1.0
-Display-If-Installed: >=sys-devel/gcc-4.7.0
+Display-If-Installed: <=sys-devel/gcc-5
Display-If-Keyword: amd64
Display-If-Keyword: arm
Display-If-Keyword: mips
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : blueness@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
^ permalink raw reply [flat|nested] 3+ messages in thread
* 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
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
2017-06-04 18:25 ` M. J. Everitt
1 sibling, 0 replies; 3+ messages in thread
From: Mike Gilbert @ 2017-06-04 16:11 UTC (permalink / raw
To: Gentoo Dev
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* 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
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
@ 2017-06-04 18:25 ` M. J. Everitt
1 sibling, 0 replies; 3+ messages in thread
From: M. J. Everitt @ 2017-06-04 18:25 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1.1: Type: text/plain, Size: 1999 bytes --]
On 04/06/17 16:55, Anthony G. Basile 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?
>
> index d074dbe..25f1712 100644
> ---
> a/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt
> +++
> b/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt
> @@ -2,9 +2,9 @@ Title: GCC 4.7 Introduced the New C++11 ABI
> Author: Anthony G. Basile <blueness@gentoo.org>
> Content-Type: text/plain
> Posted: 2014-10-26
> -Revision: 1
> +Revision: 2
> News-Item-Format: 1.0
> -Display-If-Installed: >=sys-devel/gcc-4.7.0
> +Display-If-Installed: <=sys-devel/gcc-5
> Display-If-Keyword: amd64
> Display-If-Keyword: arm
> Display-If-Keyword: mips
>
fwiw, I think although the root causes are similar, the differences
between the major GCC versions probably warrant their own separate news
items, unless there is updated information relevant to first-time
viewers. I'd probably constrain the existing news items closer to
~sys-devel/gcc-5 perhaps - or >= gcc-4.7 <gcc-6 or some-such - at the
appropriate discretion, to avoid the immediate problem you assert.
I'm not sure news has the facility to re-mark-unread existing 'read'
"old" news items, and thus re-display to users who've already seen the
original.
As a conservative user still using gcc-4.9 (for now, but ready to take
the plunge on gcc-5 [Yes, really!]) I would welcome a TL;DR on the
things to watch out for when building apps with the new major versions
of GCC going forward.
HTH,
Michael/veremit.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-06-04 18:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2017-06-04 18:25 ` M. J. Everitt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox