I have posted the problem description together
with possible solutions to the moptilities and closer-mop projects:
https://github.com/gwkkwg/moptilities/issues/1
http://sourceforge.net/p/closer/mailman/message/31656992/
On Mon, Nov 18, 2013 at 2:34 AM, Pascal Costanza p...@p-cos.net wrote:
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
18.11.2013, 08:02, Robert P. Goldman rpgold...@sift.info:
Anton Vodonosov wrote:
18.11.2013, 07:50, Robert P. Goldman rpgold...@sift.info:
Are you saying now that version 1.0.0 of Closer-MOP will satisfy the
requirement of 0.55, and that Anton should *not* be having this build
failure.
On 18 Nov 2013, at 15:54, Faré fah...@gmail.com wrote:
On Mon, Nov 18, 2013 at 2:34 AM, Pascal Costanza p...@p-cos.net wrote:
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
On Mon, Nov 18, 2013 at 10:21 AM, Pascal Costanza p...@p-cos.net wrote:
ASDF is not going to hard code an
exception for your library.
Closer to MOP already existed before asdf imposed anything on version
numbers, so asdf has to provide a way to define exceptions for such cases.
The
On 18 Nov 2013, at 16:45, Faré fah...@gmail.com wrote:
On Mon, Nov 18, 2013 at 10:21 AM, Pascal Costanza p...@p-cos.net wrote:
ASDF is not going to hard code an
exception for your library.
Closer to MOP already existed before asdf imposed anything on version
numbers, so asdf has to
OK, so we clarified what happened with :version dependencies semantics.
Now we can think what should we do with the failures, if we should.
Note, the load failures do not happen with the most
recent version of ASDF. Only with elder versions
(which are still deployed together some Lisps,
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
11 matches
Mail list logo
