[pkg-cryptsetup-devel] Bug#604936: Please move libcryptsetup to /lib

[Andreas Metzler]

On 2011-01-16 Michael Biebl <biebl at debian.org> wrote:
> On 15.01.2011 23:33, Jonas Meurer wrote:
> >> (*) They probably need to be updated to ship their devel files in /usr,
 
>> as far as I know, both packages already ship the libdevel files in
>> /usr/lib, that's why I initiated the discussion on debian-devel.

> libgpg-error-dev looks fine.

> But at least libgcrypt11-dev 1.4.6-4 does install the *.so and *.a
> file in /lib.  The *la file is in /usr/lib but there is a symlink in
> /lib (not sure why that symlink is required).
[...]


Hello,

I think FHS fully supports installation of the so link to /lib. The
so link is part of the "shared library image".

The la file is in /usr/lib because I need to keep either the la file
itself or a symlink in /usr/lib to not break other la files that list
/usr/lib/libgcrypt.la in dependency_libs.

In the medium term we want to stop shipping libtool la files anyway.
http://wiki.debian.org/ReleaseGoals/LAFileRemoval

Which leaves the question: Why is the .a library in /lib and what is
the point of la symlink in /lib?

Afaik the whole toolchain (libtool, autoconf, cmake, pkg-config,
foo-config) shares the common assumption that library and support
files (la .a) live in the same directory. Sure, I can move around
stuff but if it breaks I get keep both pieces. Nobody, except a couple
of guys on d-d cares about this cornercase. I would rather simply stop
shipping the static library than supporting a setup not supported
upstream.

cu andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'