On Tue, 2003-12-30 at 13:48, Fred L. Drake, Jr. wrote: > > > My usual response has been that it can already be done reasonably > > > using something like: > > > > > > %define topdir /some/path/to/the/top/of/my/tree > > > %define logdir $topdir/log > > > > > > some-logfile $logdir/interesting.log > > > other-logfile $logdir/another.log > > > > Which is essentially what I do now. > > Have your users complained that it's too much?
Not yet, because there aren't any <wink>. > > That's the primary motivation, for sure. The idea is that if ZConfig is > > going to be the configuration language that Mailman3 site admins use, > > I'd like to reduce to a minimum the number of options or lines of files > > they need to look at, decide about, and change. If they can simply > > define a basedir and have all the defaults be defined in terms of that, > > it would be a bonus. > > I don't know enough about Mailman3 configuration to know how what's > being done in the config file or how many decisions the site admin > needs to deal with. Is there something for each list? I'm hoping there won't. I'd like the ZConfig stuff to define only site-wide configuration stuff, like the ipaddress/port of your smtp servers, the http port and interface for the web server, etc. ZConfig might be used for list config defaults, but I'm not yet sure about that. -Barry _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
