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 <bluen...@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.
signature.asc
Description: OpenPGP digital signature