Support installing non-primary systems not explicitly defined in .asd #139
Conversation
|
I believe this is fixed on the ASDF side, which re-runs search functions with the primary name if the original name is not found. |
|
That works only if the release containing the system has already been installed. |
When using ASDF's package-inferred-system, not all systems are explicitly defined in the .asd file, and therefore do not get picked up during the metadata generation. This makes it impossible to install these subsystems directly (for example: "lil/pure/all"). This patch solves this by trying to find a system in a dist by its primary name (the part before the first slash) if it is not found verbatim. If the minimum ASDF version is upped in the future, I recommend replacing much of this with `asdf:primary-system-name`.
daewok
force-pushed
the
load-package-inferred-system-subsystems
branch
from
753890b
to
5104d83
Compare
daewok
changed the title
|
(updated title and commit message to make it more clear the issue exists when trying to install the systems) |
|
This problem bother me too. But I've used another approach – patched @quicklisp are there any change that some of these approaches will be merged into the upstream? Or probably we could make a hook instead of |
When using ASDF's package-inferred-system, not all systems are
explicitly defined in the .asd file, and therefore do not get picked
up during the metadata generation. This makes it impossible to load
these subsystems directly (for example: "lil/pure/all").
This patch solves this by trying to find a system in a dist by its
primary name (the part before the first slash) if it is not found
verbatim. If the minimum ASDF version is upped in the future, I
recommend replacing much of this with
asdf:primary-system-name.