[asdf-devel] recompiling a system when depency system changed
Robert P. Goldman
rpgoldman at sift.net
Sat Jul 7 14:18:18 UTC 2012
I am afraid that this is a known misfeature of ASDF. ASDF doesn't recursively check the freshness of depended-on systems. We left this as is, in order to avoid a more substantial rewrite, and maintain compatibility.
See bugs 627173 and 479522 (the second one should probably be retitled).
Sent from my iPad
On Jul 7, 2012, at 6:55, Anton Vodonosov <avodonosov at yandex.ru> wrote:
> 07.07.2012, 15:40, "Anton Vodonosov" <avodonosov at yandex.ru>:
>> I have a local project, it's ASDF system specifies :depends-on (#:fiveam ...)
>> The recent quicklisp delivers new version of fiveam. But when my program performed
>> asdf:load-op on that system, the system didn't get recompiled, and old .fasl files are loaded
>> (with error, because they become incompatible).
>> Is it expected behaviour of ASDF or should I dig more and isolate the problem
>> in reproducible test case?
> BTW, maybe it is important: fiveam was already loaded at the time asdf:load-op
> was performed on my system.
> asdf-devel mailing list
> asdf-devel at common-lisp.net
More information about the asdf-devel