Dear Lisp implementors,
below is the announcement for ASDF 2.016, as posted on the asdf-announce mailing-list, also accessible via its gmane mirror gmane.lisp.asdf.announce. Please have me take your list off my forwarding aliases if unappropriate.
Can you upgrade your implementation to ship with the latest ASDF? Thanks! If you're still using 2.015 (or something even older), there have been many bug fixes, robustness, portability and upgradability enhancements and a few features implemented since.
We recommend that you keep (require :asdf) working as well as (require "asdf").
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Consider this: the first hole ever dug on the moon by a man-made machine is now done. It is the most expensive hole in the history of the human race. Now, what does that mean? How do we know whether this is one of man's noblest achievements or if it is a game being played by a small group of lunatics for their own amusement — at our expense?" — Neil Postman, "Teaching as a Subversive Activity"
---------- Forwarded message ---------- From: Faré fahree@gmail.com Date: 7 June 2011 20:30 Subject: ASDF 2.016 released To: asdf-announce@common-lisp.net Cc: ASDF-devel asdf-devel@common-lisp.net
Dear CL users,
I released ASDF 2.015.12 as 2.016.
Please test, and upon success update your implementations and lisp distributions.
Since 2.015, we have the following improvements:
* Portability: Fixes for ECL, RMCL. Tweaks for CLISP. Improvements to Windows configuration, notably for LispWorks.
* Fix to load-source-op (broken in 2.014.13 - oops).
* Avoid infinite loops in defsystem in cases of bad interference between quicklisp and your source-registry.
* Small fixes regarding upgrade, compile-file* :output-file.
* Make defsystem-depends-on actually useful by allowing a system thus depended on to define the class of the system depending on it. The XCVB bridge notably relies on this feature.
* Some documentation updates. Notably, for the sake of CLISP, (require "asdf") is the new canonical way to load ASDF, instead of (require :asdf). Sigh.
* Better tests, notably wrt hot upgrade.
Happy hacking!
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The American diplomat to the Russian: "My country too is free: in the USA too anyone may freely publish the dirty little secrets of president Medvedev!"
On 6/8/11 3:17 AM, Faré wrote:
[…]
Can you upgrade your implementation to ship with the latest ASDF? Thanks! If you're still using 2.015 (or something even older), there have been many bug fixes, robustness, portability and upgradability enhancements and a few features implemented since.
[…]
Since 2.015, we have the following improvements:
Portability: Fixes for ECL, RMCL. Tweaks for CLISP. Improvements to Windows configuration, notably for LispWorks.
Fix to load-source-op (broken in 2.014.13 - oops).
Avoid infinite loops in defsystem in cases of bad interference between quicklisp and your source-registry.
Small fixes regarding upgrade, compile-file* :output-file.
Make defsystem-depends-on actually useful by allowing a system thus depended on to define the class of the system depending on it. The XCVB bridge notably relies on this feature.
Some documentation updates. Notably, for the sake of CLISP, (require "asdf") is the new canonical way to load ASDF, instead of (require :asdf). Sigh.
Better tests, notably wrt hot upgrade.
[…]
Committed to ABCL in [r13311][].
[r13311]: http://trac.common-lisp.net/armedbear/changeset/13311
On 6/8/11 07:26 , Mark Evenson wrote: […]
Committed to ABCL in [r13311][].
A quick HEADS-UP: ASDF 2.016 breaks compiling ASDF systems packaged in jars. I've located the spot where this is failing as COMPILE-FILE-PATHNAME* not performing output translations on absolute pathnames. Now I need to figure out why this was changed in ASDF, then how to wrangle in the behavior needed for ABCL.
On 6/9/11 13:18 , Mark Evenson wrote:
[…]
A quick HEADS-UP: ASDF 2.016 breaks compiling ASDF systems packaged in jars. I've located the spot where this is failing as COMPILE-FILE-PATHNAME* not performing output translations on absolute pathnames. Now I need to figure out why this was changed in ASDF, then how to wrangle in the behavior needed for ABCL.
Fixed in a possibly kludgy way in [r13315]() for which I will follow up with @asdf-devel to see if there is a better way to address.
[r13315]: http://trac.common-lisp.net/armedbear/changeset/13315
armedbear-devel@common-lisp.net