Re: [asdf-devel] [RfC] default value for *central-registry*

2009-09-24 Thread Attila Lendvai
> or whatever, and have ASDF either recurse through these directories or > go to the systems directory underneath? This would allow sharing the i would like to point out that the way asdf suggests the symlinking of systems as the default way is not too newbie friendly... a different setup would

Re: [asdf-devel] [RfC] default value for *central-registry*

2009-09-24 Thread Faré
2009/9/24 Daniel Herring : > Regarding Tobias's question, if CL/ASDF take off, I think people will want > more than one default location.  On a unix machine, they might be /usr/asdf, > /usr/local/asdf, and ~/.asdf.  On Windows, they might be C:\asdf, > C:\Windows\asdf, and $HOME\asdf (I forget the

Re: [asdf-devel] [RfC] default value for *central-registry*

2009-09-23 Thread Daniel Herring
On Wed, 23 Sep 2009, Gary King wrote: Would anyone mind ASDF coming with an additional default value of ~/.asdf/systems/? That does seem like a reasonable default for *nix. Is there an analogous spot for Windows / cygwin? Can we use, e.g., (merge-pathnames (make-pathname :directory '(:rela

Re: [asdf-devel] [RfC] default value for *central-registry*

2009-09-23 Thread Tobias C. Rittweiler
Faré writes: > What about a ASDF_PATH, or better, a COMMON_LISP_PATH ? Hopefully the > latter, with a semantics that can be shared between ASDF and XCVB, and > that allows recursion through directories instead of or in addition to > having everything in one directory with symlinks. Such behaviour

Re: [asdf-devel] [RfC] default value for *central-registry*

2009-09-23 Thread Faré
2009/9/23 james anderson : > On 2009-09-24, at 00:06 , Tobias C. Rittweiler wrote: >> james anderson writes: >>> On 2009-09-23, at 22:03 , Faré wrote: >>> What about an ASDF_PATH shell variable to be taken from getenv the first time an asdf:operate is called? (which raises questions as to

Re: [asdf-devel] [RfC] default value for *central-registry*

2009-09-23 Thread james anderson
On 2009-09-24, at 00:06 , Tobias C. Rittweiler wrote: > james anderson writes: > >> On 2009-09-23, at 22:03 , Faré wrote: >> >>> I use >>> ~/.local/share/common-lisp/systems/ >>> /usr/local/share/common-lisp/systems/ >>> /usr/share/common-lisp/systems/ >>> >>> YMMV. >>> >>> What about an ASDF_PAT

Re: [asdf-devel] [RfC] default value for *central-registry*

2009-09-23 Thread Tobias C. Rittweiler
james anderson writes: > On 2009-09-23, at 22:03 , Faré wrote: > > > I use > > ~/.local/share/common-lisp/systems/ > > /usr/local/share/common-lisp/systems/ > > /usr/share/common-lisp/systems/ > > > > YMMV. > > > > What about an ASDF_PATH shell variable to be taken from getenv the > > first time a

Re: [asdf-devel] [RfC] default value for *central-registry*

2009-09-23 Thread james anderson
On 2009-09-23, at 22:03 , Faré wrote: > I use > ~/.local/share/common-lisp/systems/ > /usr/local/share/common-lisp/systems/ > /usr/share/common-lisp/systems/ > > YMMV. > > What about an ASDF_PATH shell variable to be taken from getenv the > first time an asdf:operate is called? (which raises ques

Re: [asdf-devel] [RfC] default value for *central-registry*

2009-09-23 Thread Faré
I use ~/.local/share/common-lisp/systems/ /usr/local/share/common-lisp/systems/ /usr/share/common-lisp/systems/ YMMV. What about an ASDF_PATH shell variable to be taken from getenv the first time an asdf:operate is called? (which raises questions as to how to reset it when you dump an image) [ F

Re: [asdf-devel] [RfC] default value for *central-registry*

2009-09-23 Thread Gary King
> Would anyone mind ASDF coming with an additional default value of > ~/.asdf/systems/? That does seem like a reasonable default for *nix. Is there an analogous spot for Windows / cygwin? Can we use, e.g., (merge-pathnames (make-pathname :directory '(:relative ".asdf" "systems")) (user- h

[asdf-devel] [RfC] default value for *central-registry*

2009-09-23 Thread Tobias C. Rittweiler
I hate that I have to push a commonly shared directory onto *central-registry* for each implementation and thus have to know the rc files of every implementation. (I was recently bidden by some classic rm -rf ~, and had to redo all these kinds of infrastructure woes.) Would anyone mind ASDF comi