<p dir="ltr"><br>
On Apr 8, 2014 8:58 AM, "Steffen Sledz" <<a href="mailto:sledz@dresearch-fe.de">sledz@dresearch-fe.de</a>> wrote:<br>
><br>
> Am 08.04.2014 19:20, schrieb Khem Raj:<br>
> > On Tue, Apr 8, 2014 at 5:33 AM, Steffen Sledz <<a href="mailto:sledz@dresearch-fe.de">sledz@dresearch-fe.de</a>> wrote:<br>
> >> If a package contains a shared library *and* a binary (e.g. a related command line tool) then the soname major version *is not appended* to the package name (see debian_package_name_hook in debian.bbclass). All other problems are aftereffects.<br>
> ><br>
> > shared objects which are to be used by other independent packages (<br>
> > public .so) should be packaged separately into runtime shared object<br>
> > package which is separate from packages with binaries so that multiple<br>
> > versions of same librararies<br>
> > can be packaged on single system, your usecase seems to indicate that<br>
> > the .so is just used by this given binary you bundle together is that<br>
> > the case ?<br>
><br>
> No it is used by the binary which is part of the package *and* some other binaries.<br>
><br>
> So i've to split the package into two packages of which one contains only the shared object. Right?<br>
yes<br>
><br>
> --<br>
> DResearch Fahrzeugelektronik GmbH<br>
> Otto-Schmirgal-Str. 3, 10319 Berlin, Germany<br>
> Tel: +49 30 515932-237 mailto:<a href="mailto:sledz@dresearch-fe.de">sledz@dresearch-fe.de</a><br>
> Fax: +49 30 515932-299<br>
> Geschäftsführer: Dr. Michael Weber, Werner Mögle;<br>
> Amtsgericht Berlin Charlottenburg; HRB 130120 B;<br>
> Ust.-IDNr. DE273952058<br>
</p>