Adam P. Harris writes: >[BTW, should I CC both the BTS *and* debian-policy?]
I believe the BTS forwards anything it receives to the package's maintainer, debian-policy. I only got one copy from the list, though, so I suspect the list server suppresses duplicates. >Charles Briscoe-Smith <[EMAIL PROTECTED]> writes: >> As specified in policy, packages with shared libs generally run "ldconfig" >> from "postinst configure". > >Actually, you're wrong, that's from the Packaging Manual, not the >Policy Manual. Oh, okay. >I feel this is too much of a nit to put in the Policy Manual. I >think, instead, you should maybe submit a patch to the Packaging >Manual suggesting that one runs ldconfig with the '-n' or using the >exact library paths (not really the most portable way to write your >'debian/rules' files, but...). Actually you're wrong, that's the postinst, not debian/rules. In any case, after rereading the ldconfig man page, it seems I was completely wrong in the first place. ldconfig -n does not rebuild the cache. If you specify a library by name, you need to give the -l (manual link) option. So, it looks like neither of these will work. I'm closing the bug. -- Charles Briscoe-Smith White pages entry, with PGP key: <URL:http://alethea.ukc.ac.uk/wp?95cpb4> PGP public keyprint: 74 68 AB 2E 1C 60 22 94 B8 21 2D 01 DE 66 13 E2
