ASDF

:root BACK failure on ABCL

Bug #1260011 reported by `bg`
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ASDF
Won't Fix
Low
Unassigned
ASDF 4.0 "ASDF4"

Bug Description

ASDF 3.0.3
ABCL 1.2.1
x86-64 arch

; Use case:
(asdf:initialize-source-registry
  '(:source-registry (:tree (:root "../"))
    :ignore-inherited-configuration))

#<THREAD "interpreter" {D5C4EE6}>: Debugger invoked on condition of type FILE-ERROR
  Unsupported directory component BACK.

Use case works with SBCL 1.1.7 and CCL 1.9.

; Workaround for ABCL:
(asdf:initialize-source-registry
  `(:source-registry (:tree ,(truename "../"))
    :ignore-inherited-configuration))

Revision history for this message
Faré (fahree) wrote :

This sounds like an ABCL bug, not an ASDF bug. Come back to us if they refuse to fix it.

Revision history for this message
Faré (fahree) wrote :

Note that (:root "../") should be the same as (:root) since the root's parent is itself (if defined at all).

If you want getcwd's parent, you should probably use (parent-directory-pathname (getcwd)). truename will presumably merge with *default-pathname-defaults* which can be something altogether different (and itself a relative pathname).

Revision history for this message
Faré (fahree) wrote :

I sent a message to the armedbear-devel mailing-list. This is definitely a bug in ABCL 1.2.1. Question: should UIOP try to paper over it, by, e.g. using :up instead?

Revision history for this message
Faré (fahree) wrote :

The ABCL team is responsive, and Mark Evenson says the ABCL team is on it.
http://abcl.org/trac/ticket/335

I propose we don't bother kluging UIOP. Marking as Won't Fix.

Changed in asdf:
importance: Undecided → Low
milestone: none → version4
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.