Re: proposal: "clisp -link" should invoke "clisp-link"

[Sam S. <sd...@gn...>]

Sam Steingold wrote:
> proposal: "clisp -link" should call the script "clisp-link".
> 1. clisp-link is not in the path, so the alternative is
> `clisp -b`/clisp-link
> 2. clisp-link does not know where the clisp executable is located, when clisp 
> -link can call it with the env.var CLISP set appropriately thus enabling 
> clisp-link to run "./configure --with-clisp=${CLISP}". this would help user 
> build modules using pre-installed clisp.

on a second thought, it is easier to install clisp-link next to clisp (in 
$bin_prefix) instead of libdir (however, this will require adding clisp-link 
man pages).

clisp-link should be able to install the newly created module so that clisp 
will find them automatically, just like it will find the system-wide modules.
this means that we need to add *user-lib-directory* (in addition to 
*lib-directory*) where the new modules would be installed, defaulting to 
~/.clisp/ (similar to ~/.cpan/). It cannot be under ~/lisp because ~/lisp/**/ 
is in *load-paths* and thus is searched by load in an unpredictable order, so 
(load "postgresql") might load ~/lisp/postgresql/postgresql.fas instead of 
~/lisp/dynmod/postgresql.lisp which will not work.

also, should we add :dynamic-modules to *features*?
it would make it easier to search for the dynmod dirs in LOAD, but does it 
really matter given that DYNAMIC_MODULES are now the default?