Re: deploying CLG

"Walter C. Pelissero" <[email protected]> writes:

> I've given a cursory look at the code and I've noticed that you meant
> to try first the non-absolute pathname and then the absolute.  I
> initially understood you intended to do the other way around.  This,
> of course, reduces substantially the security risk as I saw it.

No, I actually meant to (and does) first try the absolute path. But on a
second thought I agree that this is not a very good solution. 

So I ended up removing the directory from the pathname after a shared
object has been loaded, similar to what you did before saving an
image. It is now possible to specify absolute pathnames during
development, save an image and move the shared objects around without
doing anything else when loading the image than setting LD_LIBRARY_PATH.

The default behavior of removing absolute directories can be overridden
by specifying ":absolute t" to libraries and shared objects in the
defsystem form.

-- 
Espen

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/