On Sat, Apr 06, 21:52, Andre Noll wrote
> On Mon, Apr 01, 00:57, Andre Noll wrote
>
> > > I see a static library installed by the package. Those shouldn't
> > > generally
> > > be used unless you're doing something special -- static linking makes
> > > security and bugfix updates extremely tedious. Libraries should also be
> > > split into separate binary packages, with lib${name}dev providing
> > > development files while lib${name}${so} the runtime lib.
> >
> > Yes, I had this concern as well. I'll change the build system to
> > create a shared library instead and split the binary package as you
> > suggest. I'll follow up with another reply when it's ready.
>
> Meanwhile I've addressed these two issues and fixed the remaining
> lintian warnings. Please have a look at the current "pu" branch of
> the lopsub repo (pu: proposed updates). This branch merges the various
> topic branches, notably the branch which adds the debian/ directory and
> the branch which adds support for shared libraries. dpkg-buildpackage
> now builds two binary packages called liblopsub1 and liblopsub1-dev.
>
> To create the .deb files, run something like
>
> git clone git://git.tuebingen.mpg.de/lopsub.git
> cd lopsub
> git checkout origin/pu
> git archive --prefix liblopsub1-1.0.2/ @ | xz >
> ../liblopsub1_1.0.2.orig.tar.xz
> dpkg-buildpackage
>
> This should work on debian-9 and debian-10. I've checked that the
> two packages can be installed with dpkg -i and that all projects of
> mine which depend on lopsub compile and work as before. ldd shows
> that the resulting executables are now linked against the dynamic
> library rather than the static one (which still gets installed as
> part of the -dev package).
>
> If there are further issues, just let me know.Ping Andre -- Max Planck Institute for Developmental Biology Max-Planck-Ring 5, 72076 Tübingen, Germany. Phone: (+49) 7071 601 829 http://people.tuebingen.mpg.de/maan/
signature.asc
Description: PGP signature
