David Welton wrote:
Sorry for the slow response... had some messiness with work, and guests.
src/apache-2/mod_rivet.c: during the per-interpreter
initialization 'init.tcl' is run by calling
Tcl_EvalFile on it.
The path to init.tcl is obtained from RIVETLIB_DESTDIR,
whose definition is in Makefile.am. I also changed
src/Makefile.am to reflect this. RIVETLIB_DESTDIR
is defined by substitution of the variable
RIVET_TCL_TARGET (see macro rivet_target_dir in
configure.ac). Perhaps it's suboptimal, but I only
recently started to write m4 macros for the autotools.
The exit handler was re-enabled and Tcl_DeleteInterp
called upon child exit.
The apache-1 patch I see is related to init.tcl. I forget exactly how
things work, but should we be using the PkgRequire instead of sourcing
init.tcl ?
Di David, thank you for pointing this out. In fact the solution is
an overkill of the problem. We have to go for either on way or
the other.
Rivet loads the first init.tcl file it encounters in the PkgRequire search
path: it means that (on Unix) /usr/lib/rivet0.5.0/init.tcl takes
precedence over /usr/lib/rivet0.8.0 even though you want
the latter to be sourced in.
In fact it is init.tcl which sets up auto_path to include its own
directory in the scripts search path. This implies that if more
than one install of rivet is present a whole possibly wrong or
incompatible directory can be included in auto_path.
I didn't try to bind PACKAGE_VERSION to the 'package provide xxx'
command in init.tcl (thought it must be doable using autotools),
I chose to enable the user to install the Tcl library everywhere
he/she likes using --with-rivet-target-dir
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
