John W. Baxter wrote: > On 6/1/06 9:30 AM, "Carl Fink" <[EMAIL PROTECTED]> wrote: > >> On Thu, Jun 01, 2006 at 11:18:04AM -0500, Brad Knowles wrote: >> >>> When the configuration is done in the Python language in a Python >>> script, you can let Python do all the parsing, and do the equivalent >>> of "#include" in order to pull in all your configuration details. >> Fair enough. > > A downside is that there is no "proper" place for Defaults.py and mm_cfg.py > > They are configuration, so they go into /etc somewhere. They are > executable, so they DON'T go into /etc. Not a problem with the stock > Mailman layout, but it does cause problems for one trying to match the file > system standard (such as the Red Hat packaging of Mailman, which shotguns > Mailman into several different places--and is well done).
I have custom Mailman installs (from source releases) on my systems. The way that I solve this problem, of desiring all configuration files to exist in /etc, is to hardlink /usr/local/mailman/Mailman/mm_cfg.py (and a few others) to a directory I created (/etc/mailman) on each system. I do the same for MoinMoin (a Python wiki). This way I can periodically backup etc and not have to worry about a large bloated backup of easily re-installed applications. -Jim P. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp