Faré fahree@gmail.com writes:
On Thu, Nov 3, 2011 at 21:04, Zach Beane xach@xach.com wrote:
If I'd like to extend the source registry by writing a registry configuration file somewhere, what's the best place to write that file? Is there a way to query the running system to get the answer? Is that necessary or is there some directory that is always good to use?
Unhappily, it's a bit more complicated than it ought to be, at least unless you upgrade to the latest ASDF 2.018.6. My bad.
Assuming ASDF 2.018.6, you may just put your files in either (asdf:merge-pathnames* asdf::*source-registry-directory* (first (asdf::user-configuration-directories))) or if you want something system-wide, (asdf:merge-pathnames* asdf::*source-registry-directory* (first (asdf::system-configuration-directories))) Note that you may have to (ensure-directories-exist ...) it into existence.
Is this functionality likely to be available via exported symbols in the future?
With an older ASDF, doing the right thing on both Unix and Windows is quite complex, and basically requires reimplementing these functions from ASDF 2.018.6 - including the helper subpathname if you're using an ASDF older than 2.0.17.27.
However, if you're only concerned about Unix, I don't believe that anyone on earth configured it to not be: ~/.config/common-lisp/source-registry.cond.d/ and if anyone did, whoever it is, they are probably on their own.
What was the intended way to extend the registry? Externally via some editor after reading the manual section for your operating system?
Zach