1- Do we want to support broken versions of MKCL? Was it already broken at the previous MKCL release, or is it recent MKCL breakage?

2- Wouldn't it be better to instead have a single entry for MKCL, that has :tree ... "SYS:" instead of a :directory "SYS:" and a :tree "CONTRIB:" ?

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Put your hand on a hot stove for a minute, and it seems like an hour. Sit with a pretty girl for an hour, and it seems like a minute. THAT'S relativity. — Albert Einstein

On Wed, Sep 14, 2016 at 3:45 AM, Jean-Claude Beaudoin jean.claude.beaudoin@gmail.com wrote:

Hello ASDF-devs,

After pulling all latest commits from ASDF master and thus having a ASDF 3.1.7.19 that git describes as "debian/2%3.1.5-1-514-g7b7b9f0", and patching it with the two attached patches, and using an mkcl from its latest github master head, I then get the following result:

-#--------------------------------------- Using /home/jean-claude/CL/MKCL/dev/releases/mkcl-1.1/git/mkcl.git/src/test/asdf/../../bin/mkcl Ran 61 tests: 61 passing and 0 failing all tests apparently successful -#---------------------------------------

./test/run-tests.sh -c mkcl GOOD: Loading ASDF on mkcl produces no message ./test/run-tests.sh -l mkcl Loading all these systems: ;;; Loading "/home/jean-claude/CL/MKCL/dev/releases/mkcl-1.1/git/mkcl.git/src/test/asdf/build/asdf.lisp" Done! Script succeeded