On 4/29/10 Apr 29 -2:30 PM, Faré wrote:
I'd like to freeze the main branch of ASDF tomorrow for anything but bug fixes and documentation updates.
Is there anything any of you want to commit before the freeze? Or as an exception to the freeze.
I'm thinking in particular of the stuff in asdf-ecl. Juanjo, do you think it should be merged with ASDF itself? Especially in the light of it being semi-useful on other platforms where fasls can be concatenated? It might make things nicer if there is only one file needed for ASDF.
Do we have the system dependencies right yet?
I was just looking at one of my systems that has a kind of system dependency that won't work in ASDF2 any better than ASDF Classic.
Here's what we have: a large piece of software with many ASDF entry points. I.e., there are many .asd files which could be loaded at the top level. E.g., SYS-FOO, SYS-BAR, SYS-BAZ, ...
We want all of these systems to have a common :VERSION.
What this means is all of our .ASD files have this at their head:
(asdf:oos 'asdf:load-op :SYS-VERSION)
(defsystem SYS-FOO :version #.sys-version:+version+ ...)
Unfortunately, our ASDF-LOAD of the SYS-VERSION system, which just defines a package and a constant, cannot be replaced by :system-dependencies ...
This is effectively the same problem that James Anderson pointed out some time ago, but that I didn't yet appreciate.
Do we ship with system-dependencies or try to come up with something better before shipping asdf 2.0?
best, r