Steve Langasek wrote:
Hi folks,
The libsasl2-2 package states quite explicitly that:
If you intend to use this package on a server that provides SASL
authentication, then you must install some of the libsasl2-modules*
packages.
This suggests that the modules should actually be dependencies of the
package rather than merely recommends, which is what the Ubuntu package
currently does as a result. Here is a patch that implements this:
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, libsasl2-modules (= ${Source-Version}) |
libsasl2-modules-sql (= ${Source-Version}) | libsasl2-modules-gssapi-heimdal (=
${Source-Version}) | libsasl2-modules-kerberos-heimdal (= ${Source-Version}),
${misc:Depends}
Conflicts: postfix (<< 2.3.4-3), libsasl2-gssapi-mit (<< 2.1.22), libsasl2-krb4-mit
(<< 2.1.22)
-Recommends: libsasl2-modules (= ${binary:Version})
See: http://qa.debian.org/popcon.php?package=cyrus-sasl2
Summary:
libsasl2-2 install base: 98.94%
libsasl2-modules install base: 54.72%
libsasl2-modules-sql install base: 1.17%
Personally speaking (I'm not a package maintainer), I think these
dependencies should belong in the packages that use them (such as
cyrus-imapd). libsasl2-2 itself should keep it's dependencies small.
The gssapi and sql packages have a fair amount of 3rd party dependencies
that many admins probably won't ever need.
- Dan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
