Re: How CLSQL finds and loads foreign libraries

On Thu, 9 Jun 2005 03:51:54 -0600, Kevin Rosenberg <kevin-HJRc7zDS/[email protected]> wrote:

> No, I still think it's a good method to allow programatic end-user
> modification of the search paths. For Debian, or other
> pre-configured CLSQL packages which depends on a site specific path,
> and for which those paths are to be automatically available, a
> different technique will be required.
>
> 1. Define a universal CLSQL pathname that holds the site-specific
> files. Such as "/etc/clsql-library-paths.lisp" and have CLSQL add
> the directories specified in that file on startup. I suppose this
> could replace the above clsql:push-library-path method. But, I think
> it's reasonable to have this in addition.
>
> 2. Maintain a local patch for the site-specific package. For
> example, the debian package would have a patch as below[1].
>
> What do you think of the these alternatives?

I think that option no. 2 would be a bit too much work for the Debian
maintainer.  What about option no. 1 but using an environment variable
instead of a file?  This would also work with Windows.

Cheers,
Edi.