On 12 May 2004 16:05:07 -0400, "Christopher C. Stacy" <[EMAIL PROTECTED]> wrote:

> At this point, I must repeat my call to anyone who is using ASDF.
> (So far only one person has answered, saying that they don't think
> it works with logical pathnames!)  I was under the impression that
> many people are actively using ASDF in CMUCL, and surely they must
> be using logical pathnames.  I must be totally misunderstanding how
> logical pathnames are supposed to be used, or how ASDF is supposed
> to be used.  It works for everyone but me, and I can't see how.
>
> [...]
>
> How is anyone else loading UFFI and CL-SQL ? I know there are users.
> Won't someone please just recite the incantations they are using?
> Surely the whole problem must be that I am doing something really
> stupid.

I don't use logical pathnames. My setup is very simple:

1. I have a directory /usr/local/lisp/source where I unpack all the
   source tarballs, so there is, e.g., 

     /usr/local/lisp/source/uffi-1.4.12
     /usr/local/lisp/source/clsql-2.10.5

2. I make symlinks to the names without versions, i.e.

     /usr/local/lisp/source/clsql -> clsql-2.10.5
     /usr/local/lisp/source/uffi -> uffi-1.4.12

3. From /usr/local/lisp/Registry I make symlinks to the symlinked .asd
   files
 
     cd /usr/local/lisp/Registry
     for i in ../source/{clsql,uffi}/*asd; do ln -s $i; done

   so I don't have to update them once I get new versions.

4. My ~/.cmucl-init file contains this line:

     (pushnew "/usr/local/lisp/Registry/" asdf:*central-registry*)

That's it. Works fine for me, even with different Lisps as long as
their FASL suffixes don't conflict as with SBCL and AllegroCL.[1][2]

HTH,
Edi.

[1] I think I could to something like

      (setq sb-fasl:*fasl-file-type* "sbcl")

    but I probably have to do this at build time.

[2] I understand that CLC has a more elegant solution for this but my
    approach is good enough for me.


Reply via email to