https://bugzilla.novell.com/show_bug.cgi?id=206414 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |varkoly@novell.com |screening@forge.provo.novell| |.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=206414 ------- Comment #3 from andreas.hanke@gmx-topmail.de 2006-09-20 20:01 MST ------- (In reply to comment #2)

There can (and should) be a compatibility symlink to avoid this problem.

Yes, and that's where the problem starts. Assume the following scenarios: (1) Upstream does not get informed about the issue and does not change the path. We change the path in our package and add a compatibility symlink. Result: Two file names that people start relying upon. Not nice, but not catastrophic either. (2) Upstream does not get informed about the issue and does not change the path. We change the path in our package and add a compatibility symlink. Later, upstream gets informed and changes the path, but to something else than we did, because we cannot predict which path upstream will use. Result: Not two, but _three_ file names that people start relying upon. It's getting worse. Three paths in a realistic scenario if we change the path instead of one path right now, the filesystem gets cluttered with compatibility symlinks and users will not understand that this is necessary and will ask the "why" question. Furthermore, I'd like to point out that moving config files are independently of this specific issue often perceived as an annoyance, especially if they were moved by a distributor and not the upstream authors. I don't even know why they are using this path, do you? There might be a reason. Are you aware that "constantly moving config files and deviations" is a very common view that people have about SUSE Linux? I don't want this to be(come) correct. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=206414 andreas.hanke@gmx-topmail.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tretkowski@ip-exchange.de ------- Comment #5 from andreas.hanke@gmx-topmail.de 2006-10-16 04:17 MST ------- *** Bug 212560 has been marked as a duplicate of this bug. *** -- 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.

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.

https://bugzilla.novell.com/show_bug.cgi?id=206414 rhafer@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rhafer@novell.com |varkoly@novell.com Status|ASSIGNED |NEW ------- Comment #9 from rhafer@novell.com 2006-10-27 08:50 MST ------- Fixed cyrus-sasl and openldap2 packages submitted to STABLE. Peter please take care of postfix. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=206414 suse-beta@cboltz.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED ------- Comment #11 from suse-beta@cboltz.de 2007-01-03 10:00 MST ------- VERIFIED in 10.2 final (DVD9) by reading ARCHIVES.gz: - /usr/lib/sasl2 contains only *.so* files - smptd.conf and slapd.conf are in /etc/sasl2 now Thanks! -- 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.