1 |
On 04/06/17 16:55, Anthony G. Basile wrote: |
2 |
> Hi everyone, |
3 |
> |
4 |
> Kensington suggested updating the news item on the new c++11 abi for |
5 |
> gcc. Since this news item now appears for all new installations of gcc |
6 |
> it can be annoying. I'm proposing to change it as below, but I have one |
7 |
> concern. It is important for anyone upgrading from gcc-4 to gcc-5. But |
8 |
> if an upgrade to gcc-5 removes gcc-4, then the message won't show up |
9 |
> while it is still relevant. |
10 |
> |
11 |
> Any suggestions on how to proceed? |
12 |
> |
13 |
> index d074dbe..25f1712 100644 |
14 |
> --- |
15 |
> 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 |
16 |
> +++ |
17 |
> 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 |
18 |
> @@ -2,9 +2,9 @@ Title: GCC 4.7 Introduced the New C++11 ABI |
19 |
> Author: Anthony G. Basile <blueness@g.o> |
20 |
> Content-Type: text/plain |
21 |
> Posted: 2014-10-26 |
22 |
> -Revision: 1 |
23 |
> +Revision: 2 |
24 |
> News-Item-Format: 1.0 |
25 |
> -Display-If-Installed: >=sys-devel/gcc-4.7.0 |
26 |
> +Display-If-Installed: <=sys-devel/gcc-5 |
27 |
> Display-If-Keyword: amd64 |
28 |
> Display-If-Keyword: arm |
29 |
> Display-If-Keyword: mips |
30 |
> |
31 |
fwiw, I think although the root causes are similar, the differences |
32 |
between the major GCC versions probably warrant their own separate news |
33 |
items, unless there is updated information relevant to first-time |
34 |
viewers. I'd probably constrain the existing news items closer to |
35 |
~sys-devel/gcc-5 perhaps - or >= gcc-4.7 <gcc-6 or some-such - at the |
36 |
appropriate discretion, to avoid the immediate problem you assert. |
37 |
|
38 |
I'm not sure news has the facility to re-mark-unread existing 'read' |
39 |
"old" news items, and thus re-display to users who've already seen the |
40 |
original. |
41 |
|
42 |
As a conservative user still using gcc-4.9 (for now, but ready to take |
43 |
the plunge on gcc-5 [Yes, really!]) I would welcome a TL;DR on the |
44 |
things to watch out for when building apps with the new major versions |
45 |
of GCC going forward. |
46 |
|
47 |
HTH, |
48 |
Michael/veremit. |