[Asdf-devel] Why won't accept relative pathnames in source-registry?
e.arrows at gmail.com
Thu Feb 19 04:01:35 UTC 2015
On Thu, Feb 19, 2015 at 12:48 PM, Faré <fahree at gmail.com> wrote:
> On Wed, Feb 18, 2015 at 10:40 PM, Eitaro Fukamachi <e.arrows at gmail.com>
> > Thanks for quick replies.
> >> Actually, this feature is already available, I believe, through the
> >> :HERE directive in the configuration language.
> >> This was something we added for the case that I found common, where
> >> there would be a project directory tree, with all the required code in
> >> subdirectories, and a master configuration file at the root.*
> > It is a little bit different from what I wanted to do.
> > I'm trying to run a one-liner sbcl command with adding a specific
> > to source registry.
> > Though CL_SOURCE_REGISTRY looks perfect for the purpose, it must be a
> > and doesn't accept relative pathnames.
> If the string starts with a ( it is read, and can contain :here.
> > # copying from my first email
> > # doesn't work
> > CL_SOURCE_REGISTRY=. sbcl --eval '(princ (asdf:system-source-directory
> > :myapp))'
> What's wrong with $PWD ?
Because it's longer than ".".
In shell world, people always aware of CWD and expect apps accept both of
> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
> If you think you can do a thing or think you can't do a thing, you're
> — Henry Ford
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asdf-devel