[2.90.9] planning for the next release

[Benjamin Kosnik]

> Instead of having another release, I think adding the libstdc++ tree
> into the GCC tree seems to be the next logical step to me. In my view,
> there should be an option --enable-libstdc++-v3 in Cygnus configure
> (which would be the second after --enable-gdbgui), and the libstdc++
> v3 tree would live side-by-side with the v2
> tree. --enable-libstdc++-v3 would also have effect on gcc
> configuration, such as enabling namespaces by default, having a
> different g++ include dir, and so on.

Hmm. Hmmmmm. Hmmmmmmmmmmmmm. 

I'm sure the configure script hacking would be the smallest part of this 
scenario. Most of the v3 configure work is already done. A patch would 
certainly be interesting reading--are you suggesting 
cross posting it to gcc@gcc.gnu.org? I suppose if the repository had 

libstdc++-v3
libstdc++-v2
libio-v2

Then the links could be made at configure time in the build directory, 
say to "libstdc++" and "libio". 
This might be a pain in the neck to do in CVS though, so maybe something like

libstdc++-v3
libstdc++
libio

And then soft links to "libstd++-build" and "libio-build" or something. I 
dunno.


-benjamin