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

[Ondřej Surý]

So if I understand you correctly, you want to add "/etc/sasl2" directory
to the package + on upgrades and change the documentation (perphaps
adding README.Debian to the package)?

Feel free to send a patch to accomplish that, it seems reasonable to do
this. (I am not checking the source package, since I am at home
computer, responding really quickly to you, so I don't know the current
status of the package.)

BTW cyrus-sasl2 is still in dire need of co-maintainers...

Cheers,
Ondrej


On Thu, Sep 10, 2015, at 16:17, David Magda wrote:
> Consistency.
> 
> Just about all configuration items on a Linux/Unix system are placed in 
> /etc, except for the Cyrus SASL packages where there is no 
> /etc/sasl{,2}/, but rather a /usr/lib/sasl2 (and 
> /usr/lib/x86_64-linux-gnu/sasl2). It's confusing because /etc/sasldb2 
> and /etc/saslauthd.conf are in /etc, but not smtpd.conf, slapd.conf, 
> etc., by default.
> 
> The fact that I had to run strings(1) to figure out that /etc/sasl2 is 
> even possible for the Debian packages is slightly silly IMHO.
> 
> RH/CentOS has both /etc/sasl2 and /usr/lib64/sasl2 in their RPMs 
> (without the (perhaps over-complicated?) linking) I proposed. At the 
> very least, having /etc/sasl2 in the .deb file would help in that you 
> can easy figure things out with an 'ls -ld /etc/sasl*'. As someone new 
> to SASL, /usr/lib/sasl2/*.conf is very odd:
> 
>      https://en.wikipedia.org/wiki/Principle_of_least_astonishment
> 
> I just think it would be better for everyone if things were more 
> consistent, especially those of us who are new to SASL and trying to 
> figure things out the first time.
> 
> On 2015-09-10 09:42, Ondřej Surý wrote:
> > Control: tags -1 +moreinfo
> >
> > Hi David,
> >
> > could you please describe what problem are you trying to solve?
> >
> > Cheers,
> > Ondrej


-- 
Ondřej Surý <ondrej at sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server