Comment 2 for bug 620579

Unhappily, this will not do.

1- you can't defpackage like that and expect to upgrade or even merely re-load without an error. The discrepancy in exported symbols will cause an error on many implementations.

2- you can't rely on cl-user for the symbols used in the boostrapping let form, so either we do some clever make-package in an eval-when, or we do the trivial defpackage. Packages should be relatively cheap to create. Aren't they? If they are considered expensive, then we could use make-package. cl-launch uses a conditional make-package this way.

3- I carried over a separate asdf-utilities package from ASDF 1, so that one could use the utilities independently from the system interface. But a long prefix makes it not very usable indeed. Maybe it's simpler to just export everything from ASDF (and keep the old name for backward compatibility? Or does noone rely on it?)