<div dir="ltr">Yes, Robert,  the problem was the upper case name. Everything was upper case "LE".  I have now changed it so that everything is lower case  "le"  and it works, and appears to consistently work (quirky behavior has gone away). This is the first LISP program that has forced me to use lower case ;-)  Given this is my first application of asdf I would never have figured this out. Thank you. I hope this will be classed as a bug.<br><br>For what it is worth, IMHO, at first blush, the *CENTRAL-REGISTRY* approach seems better as all the project code remains in the project. With the other approach one strangely puts (or links) the local project build file under a remote directory unrelated to the project. </div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 18, 2016 at 4:11 PM, Robert Goldman <span dir="ltr"><<a href="mailto:rpgoldman@sift.net" target="_blank">rpgoldman@sift.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 1/18/16 Jan 18 -9:28 AM, Attila Lendvai wrote:<br>
>> *Â asdf:*central-registry*<br>
>><br>
>> (#P"/home/LE/sbcl/" #P"/home/mordecai/quicklisp/quicklisp/")<br>
><br>
> i'd just put my code under ~/quicklisp/local-projects/ and forget<br>
> about ASDF configuration until it's again needed for something. you<br>
> can also use symlinks.<br>
><br>
> also, IIRC asdf:*central-registry* is obsoleted.<br>
><br>
<br>
</span>I'm even the maintainer and I still use ASDF:*CENTRAL-REGISTRY*.<br>
<br>
The new DSL and Faré's very efficient search methods provide great value<br>
if you are searching a large tree of files.<br>
<br>
They are also opaque and difficult to debug.<br>
<br>
If you have only a few directories in your search tree, IMO, you are<br>
better off just sticking to ASDF:*CENTRAL-REGISTRY*<br>
<br>
If you want to understand why ASDF can't find your system, the answer is<br>
usually just a (PPRINT ASDF:*CENTRAL-REGISTRY*) away. And the<br>
inefficiency won't kill you.<br>
<br>
I just wrote a trivial tree searcher I could make publicly available.<br>
Key advantage: it's dead simple, and you can use TRACE to see if it's<br>
doing what you want.<br>
<br>
Also, it's easy to write code to manipulate your central registry in<br>
lisp, on the fly. Typing the DSL into the REPL isn't my cup of tea.<br>
<br>
YMMV -- in particular if you have a very large set of libraries, as I<br>
have said above -- the DSL and caching can be a huge win. But for many<br>
of us, it will be overkill, and come with a high cost in lost ability to<br>
debug. Stumbling through the many function pointers, hash tables, etc.,<br>
is hard work!<br>
<br>
As long as I am maintainer, *CENTRAL-REGISTRY* will stay.<br>
<br>
Cheers,<br>
r<br>
<br>
<br>
</blockquote></div><br></div>