HAHAHAHAHA. No.
.______. _|doogie|_ <-- dpkg hat
No because of technical reasons, or because it's too much work?
IMHO: No because it is unclean/ugly/fragile/hacky/total mess/etc.
IMHO since changing library filenames breaks compatibility with other distributions, this is the only way to allow installation of old packages (that, still IMHO, must absolutely not be broken).
All c++ sarge packages will be compiled with g++ 3.2 (AFAIK). All C++ code needs to be recompiled to work (still it's better than megahacks affecting whole distribution IMHO). If you want, you can put old libstdc++ and old (locally compiled) binaries somewhere in /usr/local and create wrappers by hand (or write wrapper generator - shouldn't be hard).
-- [ Yenar Calentaure | [EMAIL PROTECTED] | http://yenar.host.sk ]
