Elizabeth Thomas wrote:
Don,
I think we would like to avoid having the install directory 'baked in'
to the nsd in any way (it enables builds to occur on different
machines/locations and the install directory be moved around as needed
without requiring rebuilds).
But but ... [ns_info nsd] exists and is used to find where nsd was
called from. The assumption that it's being run from a coherent
AOLserver install is already being made by the sample config script to
locate modules like nssock.so.
This doesn't "bake in" knowledge of the install directory in any way as
it is discovered dynamically.
Now ... it is possible that init.tcl is sourced before the directory nsd
lives in has been located, but other than that I don't see a problem
(and I doubt this is true.)
You could even look in home first and the bin directory containing nsd
if it doesn't find one in home - on the off chance existing users have
either customized it or have deleted the one in <install-dir>/bin. If
you did this it wouldn't break any existing setups.
In the Unix world it's generally assumed that once you've installed
something you don't need to keep any of the pieces around locally - not
if the app is well-behaved, anyway. That it's safe to do a make
distclean after a make install.
We already have a world convinced that Apache is the One True Webserver.
Little kinks like this are the kind of thing that might alienate someone
casually investigating AOLserver.
--
Don Baccus
Portland, OR
http://donb.photo.net, http://birdnotes.net, http://openacs.org
I. To remove yourself from this list:
Send a message to "[EMAIL PROTECTED]" with the following text in
the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/
