[asdf-devel] ASDF 2.016.2
Chun Tian (binghe)
binghe.lisp at gmail.com
Mon Jun 13 02:47:06 UTC 2011
I don't think the new feature for RMCL really working:
;Compiling "Macintosh HD:users:binghe:Lisp:packages:asdf:asdf.lisp"...
? (load *)
;Loading #P"Macintosh HD:users:binghe:Lisp:packages:asdf:asdf.cfsl"...
? (pushnew "/Users/binghe/Lisp/usocket/branches/0.5.x/" asdf:*central-registry* :test #'equal)
; Warning: Ignoring extra ")" on #<LISTENER "Listener" #x5CDDE1E> .
; While executing: #<Anonymous Function #x5A52A9E>
? (asdf:load-system :usocket)
> Error: While searching for system "usocket":
> "/Users/binghe/Lisp/usocket/branches/0.5.x/" evaluated to
> "/Users/binghe/Lisp/usocket/branches/0.5.x/" which is not a directory.
> While executing: ASDF::SYSDEF-CENTRAL-REGISTRY-SEARCH
> Type Command-. to abort.
See the Restarts… menu item for further choices.
As above test shows, I started a clean RMCL without ASDF and then manually compile&load ASDF 2.016.2, pushing only one system directory (as POSIX namestring) to asdf:*central-registry* and it fails to interpret ...
How can I debug this?
Chun Tian (binghe)
在 2011-6-12，13:12， Faré 写道：
> Regarding RMCL and logical pathnames, please test 2.016.2.
> I introduce some non-trivial pathname changes.
> On RMCL, ASDF sees strings as "/posix/namestrings/" in its configuration.
> if you want OS9-style pathnames, they are #p"that:a:way:". You can thus
> both trivially share your configuration with other implementations, and
> just as trivially use MCL-specific paths.
> For logical pathnames, I implemented my "harder way" plan
> from previous email:
>> make extra effort when using DIRECTORY against logical pathnames
>> to always reconstitute LPNs from the PPNs given by directory, and
>> drop the reconstituted results if they don't resolve to the same thing.
> In other words, if I compute (directory #p"FOO:CL;BAR;"),
> and find a file #p"/home/baz/cl/bar/quux.asd", the file will be kept
> only if (make-pathname :name "quux" :type "asd" :defaults #p"FOO:CL;BAR;")
> has the previous as its truename. And similarly when walking directories.
> I believe this restriction is not a problem in practice, and
> will keep things somewhat sane.
> And no, it's probably still not a good idea to try mix logical pathnames
> and mixed-case physical pathnames, as the result is highly non-portable.
> Also removed *system-cache* and getuid, which were bad ideas that
> never worked (and if anyone is using either, he'll thank me for making
> him stop).
> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
> I believe in God, only I spell it Nature. — Frank Lloyd Wright
> asdf-devel mailing list
> asdf-devel at common-lisp.net
More information about the asdf-devel