Re: complex versioning scenario

[Steffen Sledz <sledz@dresearch-fe.de>]

Am 08.04.2014 19:20, schrieb Khem Raj:
> On Tue, Apr 8, 2014 at 5:33 AM, Steffen Sledz <sledz@dresearch-fe.de> wrote:
>> 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.
> 
> shared objects which are to be used by other independent packages (
> public .so) should be packaged separately into runtime shared object
> package which is separate from packages with binaries so that multiple
> versions of same librararies
> can be packaged on single system, your usecase seems to indicate that
> the .so is just used by this given binary you bundle together is that
> the case ?

No it is used by the binary which is part of the package *and* some other binaries.

So i've to split the package into two packages of which one contains only the shared object. Right?

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058