Thanks, I'll try that. I still want to know if anyone knows if there's a good reference for what the builtin variables for things like this is, or if I should grovel the code/process the docstrings in the packages in some way.

On 2/14/07, Gary King <> wrote:
OK. I think that the answer is still asdf:*central-registry*. For example, mine is:

("user-home:darcs;asdf-systems;" "/repository/darcs/asdf-systems/"

(the contents of the list are evaluated when asdf searches for systems which is why some of the items are code that will evaluated into a pathname and not pathnames themselves.)


On Feb 14, 2007, at 10:38 AM, Marcin Tustin wrote:

On 2/14/07, Gary King < > wrote:
Hi Marcin,

I've not looked at BKNR for a while but when it did, it used ASDF for installation. If this is still the case, then you'll want to include the paths to the BKNR asd files (the system definitions) in the variable asdf:*central-registry*.

I hope this helps; if not, I'm probably misunderstanding the question so please ask again!

My question isn't really a  BKNR one - I just mentioned that for context. I want to know if there is a way to programmatically discover where SBCL keeps contrib code. I want to use this in config files which need to be configured with install paths.

Take Surveys. Earn Cash. Influence the Future of IT
Join's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
Sbcl-help mailing list

Gary Warren King, 
Cell: (413) 885 9127
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM