On Mon, 4 Jan 2016 17:40:11 +0100
Christoph Berg <m...@debian.org> wrote:
> Re: Herbert Fortes 2016-01-04
> <20160104143601.f6eaed358afd42577db72...@ig.com.br>
> > > I agree that webcamoid is who should be adapted.
> > >
> > > Using 'Conflicts' is the easy way for me. I'm not sure
> > > in how to put the file in something like /usr/lib/*/webcamoid/
> > > (it was suggested). How do I do to the file be found.
> > >
> >
> > I have this on Qb/commons.pri:
> > isEmpty(PREFIX): PREFIX = /usr
> > isEmpty(EXECPREFIX): EXECPREFIX = $${PREFIX}
> > isEmpty(LIBDIR): LIBDIR = $${EXECPREFIX}/lib
> >
> > And in debian/rules:
> > "LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH)"
> >
> > Is the search recursive ?
>
> If there are "external" users of that library, you need to keep it in
> /usr/lib or /usr/lib/$triplet.
>
> If there's only "internal" users like plugins built from the same
> source or the like, you could move it to a sub directory and then use
> linker magic (rpath, etc) to point the loader there, but that's all
> going to be a maintenance burden.
>
I read this on debian-policy:
"In case several development versions of a
library exist, you may need to use dpkg's
Conflicts mechanism"
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-dev
Can this be a good argument ?
regards,
--
Herbert Parentes Fortes Neto (hpfn)
