Couldn't file triggers be used, so ldconfig is triggered after any package installs a library file? That's much more how I expected triggers to be used, rather than needing an ugly ldconfig wrapper. I think it also addresses drow's point about libraries in nonstandard locations, since those packages could just run ldconfig as usual. Meanwhile, packages installing libraries to standard locations could stop calling ldconfig. -- see shy jo
Attachment:
signature.asc
Description: Digital signature