On Sat, Feb 1, 2014 at 11:02 PM, Robert P. Goldman <rpgoldman@sift.info> wrote:
On Mac OS X, when I try to upgrade my ASDF using the logical pathnames "home:lisp;asdf;" and "home:lisp;asdf;uiop;" I get this error:
*** - While searching for system "asdf": "home:lisp;asdf;uiop;" evaluated to "home:lisp;asdf;uiop;" which is not an absolute directory.
Weird. It looks like an absolute directory to me indeed. Was it parsed properly? Did you forget to use #p"...", or somehow got the pathname parsed before the logical pathname was configured?
Note that I am using ASDF:*CENTRAL-REGISTRY*, not the configuration DSL.
But:
Break 1 [2]> (translate-logical-pathname "home:lisp;asdf;uiop;") #P"/Users/rpg/lisp/asdf/uiop/"
Is this expected behavior from clisp + ASDF?
This same configuration works on ACL and SBCL, which suggests its a clisp issue.
Can you publish steps to reproduce? This works for me on CLISP 2.49+ (2010-07-17) (built 3590935887) (memory 3590936564), which I believe is actually a recently compiled CLISP from hg. (setf (logical-pathname-translations "home") '(("**;*.*" #p"/home/tunes/**/*.*"))) (translate-logical-pathname "home:cl;asdf;uiop;") (describe #p"home:cl;asdf;uiop;") (push #p"home:cl;asdf;uiop;" asdf:*central-registry*) (push #p"home:cl;asdf;" asdf:*central-registry*) (asdf:locate-system "asdf") (setf asdf:*resolve-symlinks* nil) (asdf:locate-system "asdf") (asdf:load-system "asdf") —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Nothing is particularly hard if you divide it into small jobs. — Henry Ford