Commit e0f92418 authored by Francois-Rene Rideau's avatar Francois-Rene Rideau

Stop trying to upgrade from 2.26 on CCL

Our punting strategy seems to fail, but it doesn't matter,
because CCL has always been quite up-to-date on its ASDF.
parent 1a241a5c
......@@ -426,7 +426,7 @@ valid_upgrade_test_p () {
# and only need to test it once, below for 2.24.
abcl:1.*|abcl:2.00[0-9]:*|abcl:201[0-9]:*|abcl:2.2[0-3]:*) : ;;
# ccl fasl numbering broke loading of old asdf 2.0
ccl:2.0[01]*) : ;;
ccl:2.0[01]*|ccl:2.2[0-6]*) : ;;
# Allegro ships with versions 3*, so give up testing 2
# Also, unpatched Allegro 10 has bug updating from 2.26 and before
allegro*:[12].*) : ;;
......
......@@ -124,8 +124,9 @@ Use at a given tag, put it under build/asdf-${tag}.lisp"
:allegro_64_s :allegromodern_64_s :allegro8_64_s :allegromodern8_64_s)
(version<= "2.27" tag))
;; CCL fasl numbering broke loading of old asdf 2.0
((:ccl) (or (version< tag "2.0") (version<= "2.20" tag)))
;; CCL fasl numbering broke loading of old asdf 2.0, and the punting for 2.26 fails,
;; but who cares since CCL has always been shipping recent versions of ASDF.
((:ccl) (version<= "2.27" tag))
;; CLASP is only supported as of 3.1.4.3
((:clasp) (version<= "3.1.4.3" tag))
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment