This allows for consistency check of .fasl output before the file can possibly be seen
by other builds (i.e. no race condition).

for which we do extra magic filtering. Should make Erik Pearson happy re lp#1000842.

Thanks to Erik Pearson for prompt bug report.

following discussion with Nikodemus on asdf-devel.
Also, improve the way we test for upgrade.
Disable upgrade test on cmucl from asdf 2.00*.
Restore -i.bak flag in bump-version: it's actually needed.

Update documentation somewhat.

to make Erik Pearson happy.

Fix a misparenthetization in 2.20.12 that disabled windows shortcut.

by using unintern rather than fmakunbound for redefined generic functions.

This matters if you e.g. open asdf.lisp in LispWorks before you load it,
in which case it will automatically create an ASDF package
with a default use list that pulls in symbols from LispWorks's own defsystem.
Also, export strcat.

Add a hook to autodetect file encoding.
Don't use :unspecific on ecl, it breaks asdf-pathname-test.script
Disable warnings testing when compiling asdf with SCL. Bug in SCL?

This ensures backwards compatibility with 2.20 and earlier,
for now, until the dust settles on asdf encodings.
Update documentation about encodings.
Export more utilities. Document some of them.
Remove ununspecific. Accept :unspecific on more implementations.

Make logical pathname test work on disjoint files, for now.
Fix test-upgrade wrt recent package tweak in testing.

Avoid error from missing system's source-file when upgrading from ASDF 1.

The issue fixed is that most Lisps don't like
*default-pathname-defaults* being a logical-pathname.
Added a test for logical-pathname functionality;
it all works on CCL, and works better on other Lisps after the fix,
but there are still logical-pathname issues on SBCL, CLISP and more.
Also, a package cleanup of our test suite.

Minimal documentation.

as expanded from the read-conditionals. Use (progn :default :utf-8) instead.

that's causing a warning with SBCL.

and the implementation-dependent external-format arguments.
Actually, only add a default encoding/external-format pair and
a hook to allow for an extension that would define more.
Based on asdf-devel@ discussion thread with Orivej Desh and Robert Goldman.

External format is specified via keyword :external-format per system
or per its component, the latter taking precedence.  The value is
passed then as :external-format to #'load and #'compile-file.

When unspecified, external-format defaults to UTF-8.

(in the end, the issue was not in ASDF, but the refactoring remains).

When specifying a function as output-translation,
we accept either (:function symbol) or
(:function (lambda (pathname absolute-source) ...)
The second case wasn't properly handled.
Minimal testing included.
спасибо Сергей.