[asdf-devel] Re: Unable to upgrade asdf using clisp 2.49 on Mac OS X
Robert P. Goldman
rpgoldman at sift.info
Sun Feb 2 06:19:35 UTC 2014
Thanks. I'll have a look at fixing this.
Sent from my iPad
On Feb 1, 2014, at 23:30, Faré <fare at tunes.org> 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...
> I suppose sysdef-central-registry-search and/or probe-asd could ensure
> that defaults is parsed as a pathname, using (pathname ...) or some
> invocation of (ensure-pathname ...). I leave that to you.
> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
> If you were plowing a field, which would you rather use?
> Two strong oxen or 1024 chickens?
> — Seymour Cray
More information about the asdf-devel