Dear Lisp hackers,
I am pleased to announce the release of ASDF 2.26.
Since previous release 2.25, the changes are as follow:
Portability:
* Lispworks: enable sys:get-folder-path on Personal Edition for Windows.
* ECL: add proper wrapping-source-registry -- very important.
Other:
* Package change: removed the old ASDF-UTILITIES package nickname for ASDF.
Please use the separate ASDF-UTILS system and package for utilities.
* compile-file-pathname* bug fix for :output-file nil. Fixes lp#1067617.
* get-folder-path factored out of various functions,
thanks to Martin Simmons for the suggestion:
at long last a change that REDUCES the amount of code in ASDF!
As usual, developers, please test and enjoy,
vendors, please update your implementation or distribution.
(And yes, it would be nice if Quicklisp updated its ASDF
at least once a year)
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
You think that by not releasing your in-house software, you save
engineering resources. You only get yourself out of the loop.
Currently, ASDF ignores all file types supplied by the user when specifying
a :PATHNAME value for a component. This did not happen before, though.
This is kind of annoying and hard to deal with, due to ECL's need of
prebuilt ASDF files -- these are ASDF components that contain files with
precompile sources, whose file extension need not coincide with the one
being used by ASDF at the time.
For instance, ECL may be launched with the bytecodes compiler as default
(file extension is ".fasc"), but require to load sockets.asd, which
contains the precompiled binary file sockets.fas, as in
(DEFSYSTEM "sockets" :CLASS ASDF::PREBUILT-SYSTEM :LIB #P"SYS:LIBSOCKETS.A"
:DEPENDS-ON NIL :COMPONENTS
((:COMPILED-FILE "sockets" :PATHNAME #P"SYS:SOCKETS.FAS")))
What would be the appropriate fix for this?
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
Dear Zach,
I'm a bit concerned about quicklisp shipping with a very old version of ASDF.
Quicklisp says it depends on ASDF 2.011 or later in its *required-asdf-version*,
but then you ship with 2.014.6 to load if the implementation's ASDF is too old.
Both 2.011 and 2.014.6 are antique by ASDF standards, and what more, being
older than 2.015, have trouble with self-upgrade as part of loading
other systems
that depend on ASDF. Actually, the good version for self-upgrade is 2.014.8,
but I'm rounding to the next stable release; which brings me to my next point:
2.014.6 is not just old, but it's not a supported release version (not that all
release versions are stable; 2.015 had many issues;
but the supported answer is always to upgrade to the next stable release).
What is the policy for upgrading the ASDF in Quicklisp?
If it's not "never, ever", is it possible to upgrade your ASDF to
something more recent?
For instance, quicklisp contains asdf-encodings and xcvb which depend
on asdf 2.21
for its :encoding feature, and asdf-finalizers which depends on asdf 2.23
for its :compile-check feature. Even without speaking of features,
numerous implementation-specific fixes were committed since 2.014.6,
and new implementations are supported.
Why, of all CL software, is ASDF the only one never to be updated with
Quicklisp?
Is there anything I can do to make things more comfortable for you
with respect to upgrading ASDF?
PS: I otherwise think your work with Quicklisp is wonderful.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
The penalty for laughing in a courtroom is six months in jail; if it
were not for this penalty, the jury would never hear the evidence.
— H. L. Mencken
Dear Lisp hackers,
I am pleased to announce the release of ASDF 2.25.
Since previous release 2.24, the changes are as follow:
Portability:
* Lispworks: avoid professional edition functions in personal edition.
* CormanLisp: improve support a little bit.
* Exports: don't export utilities anymore. Please use asdf-utils.
Internals:
* We stopped exporting the utilities from asdf itself.
We recommend you use asdf-utils to access the utilities in asdf.
To avoid conflicts between alexandria, fare-utils, xcvb-driver,
asdf-utils, etc., you can use xcvb-utils that solves the conflicts.
Or you can use fare-utils:define-package-mix that will help you
automatically resolve them.
As usual, developers, please test and enjoy,
vendors, please update your implementation or distribution.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
The secret of survival is: Always expect the unexpected. — Dr. Who
