In the README file (in "Source Location"):
If a system is being redefined, the top-level pathname
will be
- changed, if explicitly supplied or obtained from *load-
truename*
- changed if it had previously been set from *default-
pathname-defaults*
- left as before, if it had previously been set from *load-
truename*
and *load-truename* is not now bound
There is a minor wording issue, *load-truename* should
always be bound, but it might be NIL.
If it is NIL, asdf will try to apply TRUENAME to it. That fails
in, e.g., MCL. The README suggests that it should be ignored
in this case and the old pathname kept.
Logged In: YES
user_id=377168
This (truename ... *load-truename*is-NIL has also bitten me
when interactively defining systems at the REPL in CLISP
with asdf-1.86.1. It would be useful not to assume that
*load-truename* yields a pathname.