Abuse of IGNORE-ERRORS

[Juanjo Garcia-Ripoll]

In REGISTER-ASD-DIRECTORY, a call to DIRECTORY is wrapped in an IGNORE-ERRORS.

This is problematic because if there is a problem with the setup the user does not know but ASDF will refuse to locate any system.

As an example, in the tree ~/src/lisp I had a broken link from ~/src/lisp/update, which was a script -- nothing related to ASDF at all --. However, DIRECTORY properly complained that the "update" was not a valid object, neither a directory, nor a file, nor a link to any recognizable filesystem object. This error was obvious at the command line (see below) but was being muffled by ASDF.

I suggest being more careful and issuing a warning when ASDF can not process a given configuration line.

> (asdf:ensure-source-registry)

;;; Warning: Error when scanning system definitions in directory
 /Users/jjgarcia/src/lisp/
Error:
Filesystem error with pathname #P"/Users/jjgarcia/src/lisp/local/update".
Either
 1) the file does not exist, or
 2) we are not allow to access the file, or
 3) the pathname points to a broken symbolic link.

[Faré (fahree)]

Fixed in 1.706 (together with embarrassing bug I introduced in 1.705 that broke ECL. Oops.)