This is caused because in older ASDF, a version of 1.whatever was not
considered to satisfy a version requirement of 0.whatever. This was
changed because ASDF updated to 3.0 but was not considered satisfying
2.whatever as required by Quicklisp.
Anton Vodonosov wrote:
So, my question is: how :depends-on ((:version ...))
should work, and is the change in the behavior intentional?
There are two different version requirements.
:version is supposed to be this is the version I need. It treats
changes in the highest version component as
Anton Vodonosov wrote:
So, my question is: how :depends-on ((:version ...))
should work, and is the change in the behavior intentional?
The change of behavior in VERSION-SATISFIES is from ASDF 3.0.1, 2013-05-16.
Since even before VERSION-SATISFIES was introduced on 20/02/2002, ASDF
had been
The 0.xy versions of Closer to MOP were not based on semantic versioning, but
on an ad hoc versioning scheme. 1.0.0 did not change any API at all, so is
definitely compatible with the last 0.xy versions. 1.0.0 is supposed to
acknowledge the maturity of the library, that's it.
The FAQ section