Comment 7 for bug 627023

The joke is that:

* Towards the end of ASDF 1, Gary King created an ASDF-EXTENSIONS package, that imported (but failed to export) some utilities.
* When I released ASDF 2, I had a different, incompatible set of utilities, that I exported as ASDF-UTILITIES.
* To make bootstrapping easier, I created a package ASDF-BOOTSTRAP in which the initial update-friendly symbol/package-wrangling happens.
* Recently, Sam Steingold (of CLISP) complained that there were too many packages in ASDF, and since no one was using it, I merged ASDF-UTILITIES back into ASDF, and eliminated ASDF-BOOTSTRAP.

So we've come full circle.

In any case, I believe it is right for ASDF to export its essential utilities.
I also believe CL has a namespace management problem, but oh well.

Sorry for breaking things, but one way or the other, the ASDF API *will* change, and it is foolish to randomly (:use :asdf) and expect to never have to adapt to a modified API. If you want a fixed set of symbols, use (:import-from ...) and/or (:shadowing-import-from ...), or don't import and use fully qualified symbol names.