On 10/20/14 00:59, Duncan wrote:
Anthony G. Basile posted on Sun, 19 Oct 2014 18:59:41 -0400 as excerpted:
On 10/19/14 18:57, Jeroen Roovers wrote:
On Sun, 19 Oct 2014 18:53:43 -0400 "Anthony G. Basile"
<bluen...@gentoo.org> wrote:
we may want to inform users about breakage at the ABI level in case
they do something like add -std=c++11 to their global CXXFLAGS.
You mean tell them they get to keep the pieces?
Yes. I'm saying it politely.
The news item seems to suggest that users will be fine if they switch
/everything/ using C++ to the new standard, alto it might be a bit tough
getting to that point, but I'd guess an emerge --emptytree @world should
do it, keeping track of what breaks if anything and attempting a later
remerge of that package, which is what I've done when I've gone a year or
two between upgrades, for instance, and it has taken patience but has
worked.
I have not tested emerge -e @world and would rather not suggest anything
if someone wants c++11. I plan on testing on fresh systems from our
stage3's.
But here it looks like the intent is to say they're on their own if they
do it, even if the do it /all/ (using emptytree or the like to ensure
it's all done in at least recorded dependency order), which is a quite
different message than what I got from reading the news item.
So if you really wish to say that people electing to try c++11 are on
their own, even if they rebuild everything, the news item needs to be
reworded to say that.
I do not want to make this into a c++11 howto. I want people aware
especially so they 1) don't inadvertantly break stuff and 2) the bug
reports will be better informed.
--
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197
