Re: deploying CLG

Espen S Johnsen writes:
 > "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.

That's what "cursory looks" are all about: saving a minute now to
waste ten later.

 > 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.

Confirmed to work on CMUCL and SBCL.  Not tried under Windoze yet,
where the :absolute keyword may turn out to be useful.

-- 
walter pelissero
http://www.pelissero.de

-------------------------------------------------------------------------
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/