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

[Ondřej Surý]

Package: libsasl2-modules

Just as a note.  The .la files in modules directory are used to find
plugins (See #151567)

I wrote a patch for 2.1.24~rc1 which makes this much simpler and just
opens files ending in .so which makes thinks much simpler, but it
could break something.  So the upload will first go to experimental.

O.

-- System Information:
Debian Release: 6.0.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libsasl2-modules depends on:
ii  libc6                   2.11.2-10        Embedded GNU C Library: Shared lib
ii  libsasl2-2              2.1.23.dfsg1-7   Cyrus SASL - authentication abstra
ii  libssl0.9.8             0.9.8o-4squeeze1 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