Andres Mejia wrote: > For cases where an app uses some libs via dlopen, the dependencies for those > libs have to be manually added to control file. I want to be sure I'm using > shlibdeps mechanism to get the proper dependencies for those libs.
> It would be great if debhelper could make this easier, perhaps making use of
> ${misc:Depends} in control file, or something similar.
This is a neat idea, but I feel debhelper is the wrong layer to
implement it at, since it knows *nothing* about shlibs and symbols
files.
The right place would be dpkg-shlibdeps. Just a switch to specify
a symbol or library soname, that it could then pretend is present
in the binaries and add to its list for generating the dependencies,
would do it.
A workaround is to generate a throwaway binary that is linked against
the library you want to include but not installed, and pass it in to
dpkg-shlibdeps:
dh_shlibdeps -- throwaway
--
see shy jo
signature.asc
Description: Digital signature
