Do NOT use the central-registry if you don't know what you're doing. Use the source-registry as recommended. (Or, if you truly insist, reinitialize the central-registry after upgrade; upgrading from ASDF 2 will create a fresh ASDF package; see asdf/tools/load-asdf.lisp for how to load ASDF while supporting backward compatibility back to ASDF 1 the hard way).

Do NOT use ASDF 2.26 (from October 2012), ever. Help me convince Xach to stop distributing that bitrotting piece of maintenance nightmare. Seriously, it's a shame that Quicklisp isn't distributing ASDF 3.1.7 (from May 2016), which is the very stable culmination of the 3.1 series and works great with all its systems. And I totally understand that Quicklisp must be conservative and should not upgrade to the latest 3.2.1 (from April 2017) yet. Considering how badly ASDF 2.26 now behaves when trying to load systems from Quicklisp, I wonder if Xach even ever tests it; I bet not. Alternatively, to show how utterly ridiculous his attitude is, convince him to distribute ASDF 1.85 (from May 2004) instead, the perfect gem that Dan Barlow bequeathed us (). Or no more recent 1.366 (from September 2009), the last version wholly untainted by my code contributions.

-#f