https://bugzilla.novell.com/show_bug.cgi?id=206414 suse-beta@cboltz.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Comment #7 from suse-beta@cboltz.de 2006-10-25 06:25 MST ------- (In reply to comment #6)
If the developer of sasl hase desided to put this in /usr/lib/sasl2/ then I have to accept it. I can critique it but I have to accept his decision. This is open source development:-)
Well, beyond the argument that a config file in /usr/lib/sasl2/ violates the FHS ;-) I have news from upstream. First, have a look at the cyrus-sasl changelog: https://bugzilla.andrew.cmu.edu/cgi-bin/cvsweb.cgi/src/sasl/ChangeLog?rev=1.... 2006-04-19 Alexey Melnikov <alexey.melnikov@isode.com> * configure.in: Search for application configuration files in /usr/lib/sasl2 by default and fall back to /etc/sasl2 if not found. This means: The config file can be in /etc/sasl2/ now which is automatically used if there's no config file in /usr/lib/sasl2. Therefore we have a valid /etc config file location from upstream :-) and don't even need a compatibility symlink because the old location is still used for backward compatibility. Oh, and it's ways easier to find the config file in /etc ;-) AFAIK this change is included in SASL 2.1.22 - which is already in Factory :-) The only needed change is to put the config file to /etc/sasl2/. BTW: Debian/Etch already uses /etc/sasl2/, Gentoo probably does too (the change is based on their patch). See also this mail from Patrick Ben Koetter (german): http://listi.jpberlin.de/pipermail/postfixbuch-users/2006-October/028605.htm... (well, it contains a typo - the last sentence in section "1." should read /etc/sasl2, not /usr/sasl2 ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.