[asdf-devel] maybe hot-upgrade of ASDF is not needed anymore

Anton Vodonosov avodonosov at yandex.ru
Thu Feb 7 21:29:58 UTC 2013

08.02.2013, 01:11, "Robert Goldman" <rpgoldman at sift.info>:
> On 2/7/13 Feb 7 -2:49 PM, Anton Vodonosov wrote:
>>  Also, if user wants to use newer version of ASDF than is provided with hist CL implementations,
>>  he just loads the newer ASDF. After this, even if he does (require :asdf) the ASDF version
>>  provided by the CL implementation is not loaded, because ASDF registers itself in cl:*modules*.
>>  And Quicklisp could avoid (require :asdf). Instead it could just check if ASDF is already
>>  loaded. If it is, then use the version is loaded. If it isn't then immediately load the ASDF
>>  version shipped with Quicklisp.
> Question: is this enough for Quicklisp?  Does quicklisp ever need to
> specify a particular version of ASDF?
> I think of people running with release versions of implementations that
> are not so eagerly updated.
> E.g., if you install the SBCL that comes with your linux install,
> instead of building yourself, if you use a CCL 1.8 release, instead of
> building from svn, or if you use a commercial CL implementation....
> I had the impression that in some of these cases you might find yourself
> with an ASDF that is not sufficient to run the latest QL. Is that not so?

If user lods his own version of ASDF in the beginning, then the ASDF
distributed with CL implementation is not used. Right?

More information about the asdf-devel mailing list