Hello! Tom Jackson <[EMAIL PROTECTED]> writes: ... > be nice if it was complete, or if a sample config section for a module would > be maintained with the module, as a separate file. Even the main server has
This is a good idea and would clearly help rapid deployment. My aproach is not primarily targeted towards the Aolserver source distribution, but for packaging Aolserver in OS-Distributions like Debian Gnu/Linux, RedHat or the like, where the users want to install/uninstall a piece of software just to compare, and get frustrated if it does not fit into the System. [.. sample config, up to date doc per module, adding new modules ..] I find this all excelent ideas. Modular sourcing is almost the same aproach as taken by my scripts. I try to figure out sensible defaults, but the user can specify other defaults or divert the configuration for a specific module to a complete diferent file, thus retaining full power of configuration. > > You might also like to look at a similar effort I have been working on, > located at <http://rmadilo.com/m2/>, the starting point is jnm.tcl and > the Very interesting, may I steal some ideas? :) Regards, Jorge-Le�n -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
