Dimitri Maziuk writes: > Fair enough but I should think expecting site-specific settings to > live under /etc is no longer distro-specific and that mm_cfg.py > violates the principle of least surprise for any distro since > fsstnd.
Fair enough, but the distros already have scripts that handle this, which they would have to change. "Don't fix what ain't already broke" applies. More important, many users upgrade from source, often via local packages. Each distro does things differently. As I understand your post, RH/Centos leaves mm_cfg.py in /var/lib/mailman/Mailman and puts a link in /etc. But Debian moves the actual file to /etc/mailman, and puts a link in /var/lib/mailman/Mailman. Almost surely people are going to end up with their custom configs overwritten with the default when they upgrade. It's just not worth it for an application that's basically EOL, just to make one user with an exceptional environment happier. Regards, ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org