On tor, 2003-11-06 at 22:03, Robin H. Johnson wrote: [SNIP] > > libmysql links against libssl-0.9.6, and say you only have openssl-0.9.6 > installed at the time. > now you upgrade a slotted openssl, and have both libssl-0.9.6 and > libssl-0.9.7. > now you compile some other program that wants to pull in BOTH libssl and > libmysql. it picks up libssl-0.9.7 as that is the latest, but libmysql > is still linked against libssl-0.9.6. at this point your program > probably won't compile properly (gcc will detect the problem in most > cases), but if it doesn't your program will just segfault when you try > to run it.
Exactly what I write in the GLEP too (I use arts and kde as an example :) - my proposed solution is to put all "old libs" in a seperate directory that is not in the LD_PATH - and not accessible by portage, to make sure it doesn't pickup old libraries. And to fix this issue, a list of programs that was compiled against the old libraries should be created when the library (f.ex. openssl) is upgraded, and portage can then easily check if the program you want to compile depends on any of the programs that have been compiled with old libraries, and require them to be recompiled too. Once a program is recompiled with the new libraries, portage should just remove it from the list. -- Regards, Klavs Klavsen, GSEC - [EMAIL PROTECTED] - http://www.vsen.dk PGP: 7E063C62/2873 188C 968E 600D D8F8 B8DA 3D3A 0B79 7E06 3C62 See my new managed CMS Hosting Service at http://www.VirkPaaNettet.dk Working with Unix is like wrestling a worthy opponent. Working with windows is like attacking a small whining child who is carrying a .38.
signature.asc
Description: This is a digitally signed message part
