ASDF was never equipped to resolve versioning constraints, just to
check them. So yes, we need external tools to create assemblies of
mutually-compatible library versions. Quicklisp is such at tool, and
the only one being maintained at this point.
Otherwise, I agree that unless it is both intended
I want to highlight another tool to deal with versioning.
19.11.2013, 23:41, "Robert P. Goldman" :
> two versions of the same library on the same machine is quite feasible,
> and indeed I do this myself, every day. I have different
> source trees for different projects, and with each source tree
>
Semantic versioning makes one good thing - it concentrates
on difference between API compatible changes and API
incompatible changes.
This is an important concept and it remains valid
for binary components and for source code.
But semantic versioning is not a complete solution.
It allows to dete
