On Tue, Aug 31, 2010 at 17:44:38 (CEST), Jonas Smedegaard wrote:
> On Tue, Aug 31, 2010 at 11:10:03AM -0400, Felipe Sateler wrote:
>>On 31/08/10 08:41, Jonas Smedegaard wrote:
>>> I am not sure how to properly package non-public shared libraries.
>>> Please someone advice on this.
>> Install into /usr/lib/<package> and use RPATH on the executables using
>> it. If upstream uses autotools, I think just passing an appropriate
>> libdir will do the right thing.
> So http://wiki.debian.org/RpathIssue do not apply to all shared libs,
> only public ones?
yes. and BTW, I find rpath very acceptable for purely private shared
libraries. And even during development and local deployment, rpath is
> Currently the package generates an shlibs file and ldconfig snippets in
> postinst and postrm scripts. Lintian then complains with these:
> W: scenic-utils: postinst-has-useless-call-to-ldconfig
> W: scenic-utils: postrm-has-useless-call-to-ldconfig
ldconfig only indexes /lib and /usr/lib (and a few corner cases, but not
/usr/lib/$package, this is the point of putting them there)
> Is it wrong of dh_shlideps to include subdirectory below /usr/lib?
yes, because you do want to include the private libraries's library
dependencies, don't you?
> Is it sane to pass -X/usr/lib to dh_shlibdeps to suppress it?
no, see above.
Reinhard Tartler, KeyID 945348A4
pkg-multimedia-maintainers mailing list