On 2002.07.23 Guillaume Cottenceau wrote: >"J.A. Magallon" <[EMAIL PROTECTED]> writes: > >> When all packages are recompiled and upgraded, how will get >> libstdc++-2.96 wiped from the system ? > >Hum, there is no such mechanism. I don't know the rationale, but >I think it may be because we can't know if the user doesn't have >some binaries/libraries hand-compiled in homedir or /usr/local, >and it's not so important after all (more important to not break >the system than to not have a couple of libraries too much). >
But there is no -2.96 gcc nor libraries in Cooker. So a fresh install of 9.0 would not run anything built with 2.96. This makes an upgraded system different from a newly installed one. I personally would like a method to know my system is clean from old libs and to _break_ things that are dependent on them. How can you check if there is still something you need to rebuild ? It is important to break it, if they are not going to run on a fresh 9.0. Could there be a package like 'mdk-obsoletes' that kills everything <= given version ? If you want 9.0 to be able to run 2.96 binaries, make a libstdc++-compat or the like. So a user can clean its system (mdk-obsoletes) and if he needs install compat libs. Just ideas... -- J.A. Magallon \ Software is like sex: It's better when it's free mailto:[EMAIL PROTECTED] \ -- Linus Torvalds, FSF T-shirt Linux werewolf 2.4.19-rc3-jam1, Mandrake Linux 9.0 (Cooker) for i586 gcc (GCC) 3.1.1 (Mandrake Linux 8.3 3.1.1-0.10mdk)
