I recently tried using the latest version of ASDF on CMUCL,
and it's not working for me. It works okay in Lispworks.
The old version I had been using (version 1.30) worked okay.
This is version 1.84.
ASDF just doesn't find any of my .ASD files.
SYSDEF-CENTRAL-REGISTRY-SEARCH returns NIL.
I think maybe the problem has something to do with logical pathnames.
I'm doing it like this:
(setf (logical-pathname-translations "hl")
'(("uffi;**;*.*.*" "/home/cstacy/L/uffi-1.4.12/**/")))
(pushnew "hl:uffi;" asdf:*central-registry* :test #'equal)
(asdf:oos 'asdf:load-op :uffi)
The files exist and I can PROBE-FILE them by hand.
What could be wrong?
I do notice that the old version of ASDF had the following
hack in it. (It's possible this is something I put in).
(when (and defaults (typep defaults 'logical-pathname))
(setq name (string-upcase name)
type (string-upcase type))
But in any event, obviously ASDF works for everyone else under CMUCL.
Any suggestions?
······@news.dtpq.com (Christopher C. Stacy) writes:
> (setf (logical-pathname-translations "hl")
> '(("uffi;**;*.*.*" "/home/cstacy/L/uffi-1.4.12/**/")))
(only tangentially related: I'm sorry, I don't know what's going wrong
with your asdf/cmucl interaction)
This is odd -- you're the second person I've seen do this recently.
Why are you removing all the nice insulation against the namestring
parser that using logical pathnames buys you? Convenience, I suppose,
but... is The Right Thing not
(setf (logical-pathname-translations "hl")
`(("uffi;**;*.*.*" ; logical pathnames have defined parsing
;; but physical ones don't
,(make-pathname
:directory '(:absolute "home" "cstacy" "L" "uffi-1.4.12" :wild-inferiors)
:name :wild :type :wild :version :wild))))
?
Christophe
--
http://www-jcsu.jesus.cam.ac.uk/~csr21/ +44 1223 510 299/+44 7729 383 757
(set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b)))
(defvar b "~&Just another Lisp hacker~%") (pprint #36rJesusCollegeCambridge)
Christophe Rhodes <·····@cam.ac.uk> writes:
> ······@news.dtpq.com (Christopher C. Stacy) writes:
>
> > (setf (logical-pathname-translations "hl")
> > '(("uffi;**;*.*.*" "/home/cstacy/L/uffi-1.4.12/**/")))
> This is odd -- you're the second person I've seen do this recently.
> Why are you removing all the nice insulation against the namestring
> parser that using logical pathnames buys you? Convenience, I suppose,
> but...
Being the first person (I guess), I think I took this behaviour from
"clocc:clocc.lisp".
And I confess that even after I have been bitten I have not yet invested
sufficient time to understand pathnames well. Your improved version works
fine, and I am happy with it.
Nicolas.
Christophe Rhodes <·····@cam.ac.uk> writes:
> ······@news.dtpq.com (Christopher C. Stacy) writes:
>
> > (setf (logical-pathname-translations "hl")
> > '(("uffi;**;*.*.*" "/home/cstacy/L/uffi-1.4.12/**/")))
>
> (only tangentially related: I'm sorry, I don't know what's going wrong
> with your asdf/cmucl interaction)
>
> This is odd -- you're the second person I've seen do this recently.
> Why are you removing all the nice insulation against the namestring
> parser that using logical pathnames buys you? Convenience, I suppose,
> but... is The Right Thing not
> (setf (logical-pathname-translations "hl")
> `(("uffi;**;*.*.*" ; logical pathnames have defined parsing
> ;; but physical ones don't
> ,(make-pathname
> :directory '(:absolute "home" "cstacy" "L" "uffi-1.4.12" :wild-inferiors)
> :name :wild :type :wild :version :wild))))
> ?
I'd guess by copying code they'd seen. Personally, I knew very very
little about logical pathnames, or how parsing namestrings were
supposed to work, so my eyes just glazed over examples I'd seen. When
I recently decided to learn about logical pathnames (thanks to SBCL
not having search lists), I read the standard. Calling MAKE-PATHNAME
seemed like the only way to do it to me.
(Not that I'm happy with logical pathnames, but they're good enough
for what I'm using them for.)
--
/|_ .-----------------------.
,' .\ / | No to Imperialist war |
,--' _,' | Wage class war! |
/ / `-----------------------'
( -. |
| ) |
(`-. '--.)
`. )----'