Re: [Hamlib-developer] RFC: move backend module libs into /usr/lib/hamlib

[Stephane F. <f8...@fr...>]

Hi Kamal,

Fri, Sep 17, 2010, Kamal Mostafa skribis:
> The Debian package management system points out that the hamlib package
> doesn't quite conform with standard policy in that the names of all our
> backend module shlibs e.g. "hamlib-kenwood.so" lack version number
> information[1], which makes them ineligible for installation in /usr/lib
> where we currently install them.
> 
> I propose that we move all the "hamlib-*" libraries into a subdirectory,
> specifically /usr/lib/hamlib, which will bring them in alignment with
> policy.  For consistency, I propose moving the hamlib-*.a and the .la as
> well as the .so files into that subdirectory.  The main hamlib library
> ("libhamlib.so.2.0.12" and the symlinks that point to it) will remain
> in /usr/lib, so this will not affect normal applications which link
> against -lhamlib.  (Are there any applications which link directly
> against a backend module library??)

I agree with your proposal, and I for myslef can't see any reason not doing so.

Rem: I've never heard about applications linking directly against a backend
module library, and frankly, doing so would be quite awkward.

> 
> I request comments about the idea.  (I have implemented the simple
> changes needed, and will check it in to svn if the team approves).

Let's go ahead, check it in to svn. People will have until the release
of the next hamlib-1.2.13 to speak up.
> 
> Thanks from your friendly Debian maintainer :-)

And many thanks to our friendly Debian maintainer ;-)

73
-- 
Stephane - F8CFE