<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Aug 26, 2014, at 2:40 PM, Faré <<a href="mailto:fahree@gmail.com">fahree@gmail.com</a>> wrote:<br><blockquote type="cite">* a :source-registry entry can have a :cache entry (or be followed by<br>a :cache entry? or have a .cache file equivalent?) that lists all<br>relevant .asd files as a sorted list of relative unix-namestrings.<br>* Some script can regenerate the cache from the registry.<br></blockquote><br>Something of this kind - A disk cache of *source-registry* - is my preference de jour.<br><br>It’s trivial to dump the *source-registry* to a file and reload it. My<br>hack here along those lines is almost nothing more than a list of<br>pathnames.<br><br>The code which builds the source registry fascinates my inner archeologist;<div>I wouldn’t want to write that in bash.<br><br>It is easier to explain to users that there is one disk cache, v.s. N.<br><br><blockquote type="cite">… re-running the script when you install, deinstall or update lisp code …<br></blockquote><br>I often have very long running lisp processes. So I need to<br>do exactly that via asdf:clear-source-repository etc.<br><br>Who knows when to update/rebuild the disk cache? Sometimes<br>only the developer. But quicklisp knows when it (un)installes things.<br>I’d be tempted to update the disk cache when that happens.<br><br> - ben<br><br><div apple-content-edited="true">----<br><a href="http://enthusiasm.cozy.org">http://enthusiasm.cozy.org</a> tel:+1-781-791-3054 I forecast sunny weather!<br></div>"Communication rests on a foundation of mutual perspective-taking, the <br>mechanics of which are poorly understood."</div></body></html>