My apologies if the misunderstanding was mine. I think there's a great need for an implementation manager that forces its own ASDF, among other things.In my smalll CL implementation .rc framework I wrote, I always load a pinned ASDF, completely ignoring the host ASDF or the one in Quicklisp - and also eschewing the ASDF upgrade mechanism. I found that it worked much better and never broke in the last 4-5 years since.
My understanding is that LispWorks PE does NOT provide any version of ASDF whatsoever, that Quicklisp then provides the less-than-useful ASDF 2.26, and that the user tries to load an ASDF 3 on top of that. Which can't work.> On Thu, May 4, 2017, 13:20 Stelian Ionescu sionescu@cddr.org wrote:>>
The main thing is: do NOT use ASDF 2. Please address your complaints to Xach for the disservice of providing it.>>
Fare, do try to read more thoroughly what you're replying to. The old ASDF here is the one bundled with LispWorks PE, not the one in Quicklisp.>> -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.
-- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.