Bug#798462: libsasl2-2: recreate and use /etc/sasl2/ for new installations

[David Magda]

Package: libsasl2-2
Version: 2.1.26.dfsg1-13
Severity: wishlist

The upstream code uses /etc/sasl2/ as the default configuration directory,
as is illustrated in libsasl2.so:

$ strings /usr/lib/x86_64-linux-gnu/libsasl2.so.2 | grep etc
sasl_auxprop_getctx
/etc/sasl2:/etc/sasl:/usr/lib/x86_64-linux-gnu/sasl2:/usr/lib/sasl2

However the Debian package, for new installations, uses the last-on-the-list
directory /usr/lib/sasl2/. Would it be possible to start using /etc/sasl2/
going forward?


Perhaps something like the following for Debian 9/stretch:
 * new installation:
   * create /etc/sasl2/, put files there
   * link /usr/lib/sasls2 to /etc/sasl2
 * upgrade:
   * check for presense of /etc/sasl2 and /usr/lib/sasl2
     * if both exist, do nothing
     * if only one exists, link the other to it
       * /usr/lib/sasl2 will probably exist, so link /etc/sasl2 to it
 * update documentation to refer to /etc/sasl2 exclusively
 * add a README to inform folks that /usr/lib/sasl2 is depreciated, and
   they should put/move all file from it to /etc/sasl2 

Then in Debian 10/buster, don't create /usr/lib/sasl2 in the .deb file. Also
perhaps try removing it completely from the search path early in the release
cycle.


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libsasl2-2 depends on:
ii  libc6                2.19-18
ii  libsasl2-modules-db  2.1.26.dfsg1-13
ii  multiarch-support    2.19-18

Versions of packages libsasl2-2 recommends:
ii  libsasl2-modules  2.1.26.dfsg1-13

libsasl2-2 suggests no packages.

-- no debconf information