Well we've entered the philosophical realm here... I agree 100% with you. The Unix way is to give the power to the user and "let them shoot their foot off" if that's what they want (or at least what they tell the system they want to do).
Barry moved the URL section out of the config_list dump/input and out of the Web-admin so that folks couldn't change it easily. We had a lot of users screwing around with the value and then breaking their ability to get back to the Web-admin. This is mega-bad for folks who are simply running a hosting service. By that logic I can see removing it from the Web-admin, but IMO it should have been left in the config_list dump. So, if I can easily hack the config_list command to include changing the url then I'll do that, and put it where other folks can get to it. That way you can use a tool you are more comfortable with and which is already documented to do the job. Yeah - Open Source! Jon Carnes On Tue, 2003-02-04 at 23:25, James Devenish wrote: > In message <[EMAIL PROTECTED]> > on Wed, Feb 05, 2003 at 11:22:38AM +0800, James Devenish wrote: > > In message <[EMAIL PROTECTED]> > > on Tue, Feb 04, 2003 at 10:09:25PM -0500, Jon Carnes wrote: > > > Look at ~mailman/bin/fix_url.py. > [...] > > I wasn't clear on when I would be prompted for an address. > > Whoops, I now see that the description is on the """ line, above the > synopsis sentence. But the code makes it look like it sets the list's > web address to be the same as the default, and the list then uses that > stored value rather than the default. So I would people generally have > to consider doing fix_url when doing a site-wide web address change? > > General questions (almost rhetorical, since Mailman seems to be working > for me for the time being): > - is this behaviour generally true of the way mm_cfg.py is used > by Mailman? > - should Mailman users expect other hidden variables to require > updating in a migration? (Though, given everything we changed > in our system, it does seem to be the only problem.) > > The reason I ask if that this extra migration step is something that > we were not exposed to during installation or regular maintenance, > and which I have failed to intuitively find in the various "lister > server admin" docs. > > > > ------------------------------------------------------ > Mailman-Users mailing list > [EMAIL PROTECTED] > 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/ > > This message was sent to: [EMAIL PROTECTED] > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
