On fre, 2003-11-07 at 09:59, Paul de Vrieze 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. > > btw. This is exactly the problem with berkeley db, and it is quite common > for berkeley db. > And for a lot of other programs unfortunately. This is the thing that for me is the biggest show-stopper, for server systems - as it requires a lot of wellplaced thought and work, before you upgrade f.ex. OpenSSL (which has been requireing upgrades quite often recently :( )
I hope you can find time to look at my rewritten GLEP and see how you like it. I've detailed how I think it should be implemented, and it is in now way a performance killer, but AFAIK it should catch every occurence of this problem. -- 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
