Towards release 3.1.6

[Anton Vodonosov]

If you are interested, this version of ASDF fails on SBCL 1.0.58:

; caught ERROR:
;   READ error during COMPILE-FILE:
;   
;     Symbol "PRINT-BACKTRACE" not found in the SB-DEBUG package.
;   
;       Line: 4307, Column: 29, File-Position: 210191
;   
;       Stream: #<SB-SYS:FD-STREAM
;                 for "file /home/testgrid/quicklisp-asdf3/asdf.lisp" {ADDDA29}>


10.10.2015, 13:16, "Anton Vodonosov" <avodonosov at yandex.ru>:
> Ok, will do (sorry, read this message only today)
>
> 10.10.2015, 10:13, "Faré" <fahree at gmail.com>:
>>  All tests pass for ASDF 3.1.5.20 on Linux x64 for:
>>  ccl clisp sbcl ecl ecl_bytecodes cmucl allegro lispworks mkcl abcl allegromodern
>>
>>  Anton, can you run cl-test-grid against it?
>>
>>  —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
>>  A child of five would understand this. Send someone to fetch a child of five.
>>          — Groucho Marx
>>
>>  On Tue, Oct 6, 2015 at 9:05 PM, Faré <fahree at gmail.com> wrote:
>>>   With the sbcl/windows regression on uiop:run-program fixed (1),
>>>   and the lib-op and monolithic-lib-op features reasonably implemented
>>>   on all implementations beyond ECL & co (though requiring a CFFI patch),
>>>   I believe we're all set for ASDF 3.1.6.
>>>
>>>   Anton, do you have time to make a test run of cl-test-grid?
>>>
>>>   If some of you believe the C linking features should (or shouldn't) be included
>>>   in this release (or the next one), now is the time to voice your opinion.
>>>   It's 300 to 400 more lines of code — or 800 if we splurge and merge in
>>>   most of lisp-invocation as we go instead of special-casing it.
>>>
>>>   (1) A real fix requires fixing SBCL.
>>>   https://bugs.launchpad.net/asdf/+bug/1501373
>>>
>>>   —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
>>>   When you've seen one nuclear war, you've seen them all.