David Engel writes ("Re: ncurses-1.9.8a ELF release"):
> Let's say I have a package named foo-n with a shared library in it
> named libfoo.so.x.y that, at least for the time being, must always be
> available by that name, even while dpkg is moving things around. Now,
> at some point in the future, I know that libfoo.so.x.y whill no longer
> be needed for any number of reasons. What I'd like to be able to do
> after dpkg is done upgrading foo-n with foo-m, removing foo-n
> completely or replacing foo-n with bar-p, is have libfoo.x.y deleted,
> if and only if, no remaining package claims to own libfoo.x.y. Can
> this be done, and if so, how?
"Claims to own"? Do you mean "claims to need" ?
And is "foo-n" the package name, or is "foo" the package name and "n"
the version ?
Sorry, I'm still confused.
What I meant was that, supposing you upgrade libc5 from 5.0.9-1 to
5.2.7-1, you find that the old package contains libc.so.5.0.9 and the
new libc.so.5.2.7. The link needs to be changed to point at 5.2.9
when *both* files are available, surely, as otherwise it will point
into nowhere for a bit ?
Ian.
