Re: How CLSQL finds and loads foreign libraries

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

The shared library objects are for use only with CLSQL whereas libpq
is used by other applications. Here's a representative statement:

http://lists.debian.org/debian-mentors/2001/10/msg00038.html

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

Very good. I'll look forward to it.

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

Yes, that is a bit troublesome. One technique to require users to load
to load the CLSQL ASDF package before CLSQL-POSTGRESQL if they need to
specify a site specific library. For example

(asdf:operate 'asdf:load-op 'clsql)
(clsql:add-library-path PATHNAME)
(asdf:operate 'asdf:load-op 'clsql-postgresql)

While this technique as merit, it won't work for the Debian package
since Debian users rightfully expect (clc-require 'clsql) to work
without site specific changes. Still, this would solve most people's
needs.

Kevin

 ris to *not* allow one to
load CLSQL-POSTGRESQL until CLSQL is loaded. To automate this,
clsql-postgresql.asd could have something like:


-- 
Kevin Rosenberg
kevin-HJRc7zDS/[email protected]