component-version (version slot) unbound on ASDF after upgrade
Bug #665724 reported by
Robert P. Goldman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ASDF |
Fix Released
|
Low
|
Faré |
Bug Description
I think that the value asdf:*asdf-version* should be assigned to the VERSION slot of the system object named ASDF on load of ASDF 2.
I'm pretty sure that (asdf:component
To post a comment you must log in.
Fare writes
>
> Should we rename our current 2.140+ branch to 2.010.1 ?
> Or at some point start using 2.200 and 2.200.1 instead of 2.200 and 2.300 ?
> Or converge towards the second Feigenbaum constant?
>
Response...
I think we need to jump to something that will make ASDF's version-satisfies happier.
I think 2.010.1 is version-less-than 2.140...
We should probably move to 2.200.
Honestly, I think jumping to 3 and then going up by 3.1.0, 3.1.1 .... jump to 3.2.0, ... and so forth, would be better from the version-satisfies standpoint.
Unfortunately, since we marked things as ASDF3 in the launchpad, that's probably not a good thing to do.
I'd like us to get to a
Major version . minor version . patchlevel
discipline at some time, though.