I believe the answer to this question must be found
in the way extensions are loaded by tcl. The problem
still exists in various cases:
- for developers wanting to have more rivet installations
to switch from a module version to another without
reinstalling the whole set of libraries (the current scripts
in 'trunk' copy everything in /usr/lib/rivet and don't handle
this case)
- It might also be a problem for users who compile
and install the module on their own if they don't remove
a previous release's directory.
-- Massimo
Massimo Manghi wrote:
Hi,
what is the way by which the module understands where
the tcl code is located? I'm trying to figure out
how the module determines the path to the init.tcl
script when calling
if (Tcl_PkgRequire(interp, "RivetTcl", "1.1", 1)) {
...
}
For example: on my system the 1_0 is labeled as 0.7.0
in configure.ac, still after apache is started
auto_path had /usr/lib/rivet0.5.0 (from another installation).
Since I found no erroneous references to that version
number in the code I simply wiped out the /usr/lib/rivet0.5.0
directory, restared apache....et voila...the /src/lib/rivet0.7.0
got into the auto_path. Is it a magic of Tcl_PkgRequire?
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
