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.

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.

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.

In case you haven't guessed, I'm not a fan of this standard! :-)

On March 12, 2014 10:10:20 PM CDT, Daniel Herring <dherring@tentpost.com> wrote:
On Wed, 12 Mar 2014, Robert P. Goldman wrote:

 ~/asdf-local-paths/

 would work for me.

 Squawks sooner rather than later, please.

If we are decided on adding a default path, please make it consistent with 
the other XDG stuff in ASDF...

I'm not XDG guru, but here's a link to the standard...

http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html

It looks like default paths would belong under $XDG_DATA_HOME and 
$XDG_DATA_DIRS.

Looking at the current ASDF manual, it appears that there is already some 
support for this concept?

http://common-lisp.net/project/asdf/asdf.html#Controlling-where-ASDF-searches-for-systems

""
The source registry will be configured from a default configuration. This 
configuration may allow for implementation-specific systems to be found, 
for systems to be found the current directory (at the time that the 
configuration is initialized) as well as :directory entries for 
$XDG_DATA_DIRS/common-lisp/systems/ and :tree entries for 
$XDG_DATA_DIRS/common-lisp/source/. For instance, SBCL will include 
directories for its contribs when it can find them; it will look for them 
where SBCL was installed, or at the location specified by the SBCL_HOME 
environment variable
""


Later,
Daniel


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.