[You (Kai Henningsen)] >[EMAIL PROTECTED] (Rob Browning) wrote on 23.12.97 in <[EMAIL PROTECTED] >re.csres.utexas.edu>: >> "Adam P. Harris" <[EMAIL PROTECTED]> writes: >> > I think you're (a bit) unduly alarmed. From my interpretation, it's >> > not a bug to call `ldconfig' from postinst, it just shouldn't be >> > necessary. So why do it if it doesn't have to be done?
>> You must call ldconfig from the postinst if you install shared >> libraries. This has come up recently several times, and the Debian >> policy manual is wrong [1]. We need to change the docs so that people >> will stop asking about this. >> [1] According to the ldso maintainer. Correction: the document at issue is the "Debian Packaging Manual", not the policy manual. >> In my experience, the warnings have come from dangling symlink in the >> lib directories. I'm not sure how they get there. >What we need most is a coherent explanation of what happens, why it >happens, and why the usual strategies are right or wrong. >Seems as if the ldso maintainer and the dpkg maintainer were the two best >candidates to providing that explanation. Maybe that's not necessary. Rob Browning post got me thinking: even if you create the symlink in `debian/tmp/...', order it properly w.r.t. the actual shared lib, you do still need to call ldconfig in postinst in order to update /etc/ld.so.cache. Is this the issue? It would be a pretty simple addition to Ch 12 of the Packaging Manual. .....A. P. [EMAIL PROTECTED]<URL:http://www.onShore.com/>
