Changeset 13692


Ignore:
Timestamp:
11/03/11 16:10:07 (9 years ago)
Author:
Mark Evenson
Message:

Enable ASDF to load from jar files again for #181.

Unsure if we need to somehow change the semantics of how
MERGE-PATHNAMES works in the presence of JAR-PATHNAMES. Currently, we
have the following behavior:

CL-USER> (merge-pathnames "/home/evenson/work/abcl/dist/abcl-contrib.jar" #p"jar:file:/foo/bar.jar!/fee/")
#P"jar:file:/foo/bar.jar!/home/evenson/work/abcl/dist/abcl-contrib.jar"

Should we "break" ANSI here, so that if we have a defaulted DEVICE, we
also keep the defaulted DIRECTORY? Unfortunately, I think this will
break some common cases of dealing with relative directories inside a
JAR-PATHNAME. Need to consider this with email to both
@armedbear-develop and @asdf-develop.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/abcl/src/org/armedbear/lisp/asdf.lisp

    r13691 r13692  
    17071707                   (*default-pathname-defaults*
    17081708                    (pathname-directory-pathname pathname)))
     1709               ;;; XXX Under ABCL, if the PATHNAME is a JAR-PATHNAME the
     1710               ;;; MERGE-PATHNAMES are perhaps a bit wonky.
     1711               #+abcl
     1712               (when (ext:pathname-jar-p pathname)
     1713                 (setf *default-pathname-defaults*
     1714                       (make-pathname :device nil :defaults *default-pathname-defaults*)))
    17091715               (asdf-message (compatfmt "~&~@<; ~@;Loading system definition from ~A into ~A~@:>~%")
    17101716                             pathname package)
Note: See TracChangeset for help on using the changeset viewer.