Re: How CLSQL finds and loads foreign libraries

On Wed, 8 Jun 2005 13:59:42 -0600, Kevin Rosenberg <kevin-HJRc7zDS/[email protected]> wrote:

> Specifically, I'm working on making your patch work for the CLSQL
> debian package. Debian policy requires the shared library objects to
> go into a private directory under /usr/lib. Currently, I'm using
> /usr/lib/clsql.

But why is, say, libpq.so in /usr/lib?  What makes the PostgreSQL
package different from the CLSQL package?

> For situations like Debian while a path is required outside the
> source directory, user homedirectory, and outside the system paths,
> what mechanism is there to specify an absolute pathname?

That part isn't done yet but I think it shouldn't be too hard.  I plan
on submitting a patch for this in the next days.

My main problem, though, is to find a way to enable this user
customization while one is still able to conveniently use CLSQL.  I
mean, at the moment I can build an ASDF system definition that just
depends on, say, :CLSQL-POSTGRESQL.  If I have libpq.dll/libpg.so in a
non-standard location what do you think would be the best way to
tackle this?  After all, packages like CLSQL are only available
/after/ loading the library.

Cheers,
Edi.