cl-launch extracts the .asd file from cl-launch.sh, and thus doesn't include it in its git. Usually it's extracted by the Makefile's target source or install_source, but we try to keep the git checkout pristine except for the build/ directory (though, unhappily, test/ is also touched, and even the main asdf/ directory, by some test and release scripts).
The asdf-tools script has its own defsystem "cl-launch/dispatch" to work around that. What are you trying to do? You may want to make -C ext/cl-launch source, or to emulate the defsystem used by asdf-tools. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org If the human mind were simple enough to understand, we'd be too simple to understand it. — Pat Bahn On Sun, Jan 10, 2016 at 11:34 AM, Robert Goldman <rpgold...@sift.net> wrote: > I tried to load the asdf tools interactively, under SLIME, and they fail > to launch, although everything seems to run from make. > > I get this error: > > Component "cl-launch/dispatch" not found, required by > #<PACKAGE-INFERRED-SYSTEM "cl-scripting/commands"> > > and, indeed: > > ~/lisp/asdf/ext/cl-launch $ find . -name '*.asd' > ~/lisp/asdf/ext/cl-launch $ > > I see this: > > ~/lisp/asdf/ext/cl-launch $ git status > HEAD detached at 220b8ca > nothing to commit, working directory clean > ~/lisp/asdf/ext/cl-launch $ > > Is this another oddity of git submodules? Is the version of cl-launch > in our git repo not sufficiently up-to-date? > > Actually, when I look at xcvb/cl-launch, there is no cl-launch.asd > there, either. > > This is crippling my ability to fix 1532464 >
