Bug#516833: Are the libtool .la files, static plugins and .so-symlinks really necessary?

[Daniel Leidert]

Package: libsasl2-modules
Version: 2.1.22.dfsg1-23
Severity: wishlist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

libsasl2-modules contains a bunch of statically linked plugins, libtool
.la files and .so-symlinks in /usr/lib/sasl2/. I wonder, if they are
really necessary? Ditto for /usr/lib/sasl2/libsasldb.{a,la,so} in
libsasl2-2.

If you provide them by intennion, please simply close this report. If
they are not really necessary, please consider removing these files.

Regards, Daniel


- -- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (850, 'unstable'), (550, 'stable'), (500, 'oldstable'), (110, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libsasl2-modules depends on:
ii  libc6                    2.7-18          GNU C Library: Shared libraries
ii  libsasl2-2               2.1.22.dfsg1-23 Cyrus SASL - authentication abstra
ii  libssl0.9.8              0.9.8g-15       SSL shared libraries

libsasl2-modules recommends no packages.

Versions of packages libsasl2-modules suggests:
pn  libsasl2-modules-gssapi-mit | <none>     (no description available)
pn  libsasl2-modules-ldap         <none>     (no description available)
pn  libsasl2-modules-otp          <none>     (no description available)
pn  libsasl2-modules-sql          <none>     (no description available)

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkmjFQsACgkQm0bx+wiPa4zXewCguZjvt3xBBLS8OkkFC9HftIe8
aiAAoIXV/ZAzOTdQVanFFs2v9FecYziN
=kDSq
-----END PGP SIGNATURE-----