Scripsit Joachim Reichel <[EMAIL PROTECTED]> > Uups, I missed that I might have to change the name of the library > itself. Or is it possible to have a package named "libcore++1" > containing libraries "libcore.so.1"? (If yes, there is still the > problem that a quite generic (file)name is used.)
Unless there are two pacakges that provide technically interchangeable implementations of the same functionality, there is no reason to make package names more unique than the sonames of the libraries they provide. If the upstream source is written to create libcore.so.1 and there is no known conflicts with other libraries using the same name, I think Debian should provide the library under the same name. Client application source will be written to use -lcore, and we'd do nobody a service by forcing Debian users to change that manually. -- Henning Makholm "Hele toget raslede imens Sjælland fór forbi."