8 Apr
2015
8 Apr
'15
8:57 p.m.
On Feb 1, 2014, at 22:25, Faré fare@tunes.org wrote:
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"...",
I didn't use #p when setting ASDF:*CENTRAL-REGISTRY*, but I don't use it on SBCL or ACL, either. The central registry has always accepted namestrings for me, with this one exception...
Cheers, R