<html><head></head><body>I am sorry, but I promise you that this will NOT be consistent with XDG. I have no idea why those people think it's a good idea to put files in directories where ls cannot find them.<br>
<br>
ASDF already has a deeply-nested, invisible-to-ls location that is XDG compliant where you can put your files if that's what floats your boat.<br>
<br>
It was writing a description of where to put your files in this XDG-compliant location that convinced me that we needed an alternative that was obvious and easily accessible.<br>
<br>
In case you haven't guessed, I'm not a fan of this standard! :-)<br><br><div class="gmail_quote">On March 12, 2014 10:10:20 PM CDT, Daniel Herring <dherring@tentpost.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On Wed, 12 Mar 2014, Robert P. Goldman wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> ~/asdf-local-paths/<br /><br /> would work for me.<br /><br /> Squawks sooner rather than later, please.<br /></blockquote><br />If we are decided on adding a default path, please make it consistent with <br />the other XDG stuff in ASDF...<br /><br />I'm not XDG guru, but here's a link to the standard...<br /><br /><a href="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html</a><br /><br />It looks like default paths would belong under $XDG_DATA_HOME and <br />$XDG_DATA_DIRS.<br /><br />Looking at the current ASDF manual, it appears that there is already some <br />support for this concept?<br /><br /><a
href="http://common-lisp.net/project/asdf/asdf.html#Controlling-where-ASDF-searches-for-systems">http://common-lisp.net/project/asdf/asdf.html#Controlling-where-ASDF-searches-for-systems</a><br /><br />""<br />The source registry will be configured from a default configuration. This <br />configuration may allow for implementation-specific systems to be found, <br />for systems to be found the current directory (at the time that the <br />configuration is initialized) as well as :directory entries for <br />$XDG_DATA_DIRS/common-lisp/systems/ and :tree entries for <br />$XDG_DATA_DIRS/common-lisp/source/. For instance, SBCL will include <br />directories for its contribs when it can find them; it will look for them <br />where SBCL was installed, or at the location specified by the SBCL_HOME <br />environment variable<br />""<br /><br /><br />Later,<br />Daniel<br /><br /></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>