Hi, I'm under the impression that any shared library *must* have a SONAME. I can't find that precise statement in the policy manual, but section 11.3 says the package must be named "librarynamesoversion".
If true, what is the procedure for packaging, say Inventor, that builds two shared libs without a SONAME? I suppose the best option is to bug upstream until they give me a version to use, and that's what I intend to do. If, for the sake of argument, upstream is unwilling to commit to a version number, should one just make it up? Start with version 0? Major version of the package? Or can one leave off the SONAME entirely? Thanks, -Steve -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants
