On Wed, Mar 12, 2014 at 7:24 PM, Zach Beane <xach@xach.com> wrote:
Faré <fahree@gmail.com> writes:
On Wed, Mar 12, 2014 at 6:07 PM, Pascal Costanza <pc@p-cos.net> wrote:
Can I set CL_SOURCE_REGISTRY to a value that deactivates all "default" paths? Then I don't care what the default is...
Yes, the example I gave you did that:
export CL_SOURCE_REGISTRY=~/lisp//
As you can see with (asdf::parse-source-registry-string "/home/tunes/lisp//"), it expands to: (:SOURCE-REGISTRY (:TREE "/home/tunes/lisp") (:IGNORE-INHERITED-CONFIGURATION))
The double-slash "//" is significative: it means recurse through the directory.
Those readers who do want to inherit the configuration should just add a colon ":" at the end — or a semi-colon, if using Windows: export CL_SOURCE_REGISTRY=~/lisp//:
Alternatively, you can put this in your ~/.config/common-lisp/source-registry.conf: (:source-registry (:tree (:home "lisp")) :ignore-inherited-configuration)
Instructions like these are one of the reasons I have been unable to make or recommend regular use of the source registry configuration system.
You could also mkdir -p ~/.config/common-lisp/ echo "\"$HOME/lisp//\"" > ~/.config/common-lisp/source-registry.conf I don't know what kind of instructions you want. Having good defaults is precisely what makes such instructions superfluous for beginners, and why Robert wants to define a better default location for code than currently used. Having instructions is still necessary for people who want to override the defaults — and anyone who wants to release software built in a controlled repeatable way needs understand how to do that. If you have a better design to offer, I'm sure Robert is listening. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Verbal constructs of above-average phonemic quantity implement the qualitative actualization of cognitive disenlightenment. (Big words obscure meaning.)