Upgrade failures for asdf-3.1.7 and later
rpgoldman at sift.net
Thu May 4 18:35:21 UTC 2017
On 5/4/17 May 4 -1:17 PM, James M. Lawrence wrote:
> As I said, LispWorks PE provides an old ASDF. To verify this,
> * download LispWorks Personal Edition
> * launch it
> * (require "asdf")
> * (asdf:asdf-version)
> Again, I am writing on behalf of users, not myself personally. I don't
> use LispWorks PE or any LispWorks version for development. Others use
> LispWorks PE. Some do so to evaluate not only LispWorks but Common
> Lisp as a language. It seemed reasonable to prevent them from getting
> into a borked state, if possible (and not too difficult or annoying).
I'm not sure what is the proper solution. Should we detect this kind of
condition and raise an error if ASDF is not reconfigured after an upgrade?
> On Thu, May 4, 2017 at 1:35 PM, Faré <fahree at gmail.com> wrote:
>> 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 at 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.
More information about the asdf-devel