Faré wrote:
Actually, the asdf initialization routine could unconditionally
add the asdf tree to the path: either it's present or not, but it
doesn't hurt to try,
and so no need to export ASDF_DEVEL_SOURCE_REGISTRY, then.
I'm not entirely sure about this. Here's my question: if someone is
Faré wrote:
Thanks. BTW, isn't my ROOT_DIR definition a good replacement for your
sourceDirectory? I believe the latter could fail if the Makefile is
invoked from another directory
sourceDirectory is actually gwking's. Did five years already go by?
But to answer your question, make
Thanks. BTW, isn't my ROOT_DIR definition a good replacement for your
sourceDirectory? I believe the latter could fail if the Makefile is
invoked from another directory
sourceDirectory is actually gwking's. Did five years already go by?
But to answer your question, make -C .../asdf/
Would changing (:tree path) so it accepts an optional argument be less adhoc?
Possibly (:tree path key (depth nil) (don-not-recure-after-asdf-encountered
nil))
That said this would have little if any value in my use case. I point ask it
to sweep over my
the directory where all my coding
On Tue, Aug 26, 2014 at 1:40 PM, Ben Hyde bh...@pobox.com wrote:
Would changing (:tree path) so it accepts an optional argument be less
adhoc?
Possibly (:tree path key (depth nil)
(don-not-recure-after-asdf-encountered nil))
I of course thought about this, but it's the wrong thing:
the
Ben Hyde wrote:
Would changing (:tree path) so it accepts an optional argument be less
adhoc?
Possibly (:tree path key (depth nil)
(don-not-recure-after-asdf-encountered nil))
That said this would have little if any value in my use case. I point
ask it to sweep over my
the directory
On Aug 26, 2014, at 3:22 PM, Robert P. Goldman rpgold...@sift.info wrote:
Ben Hyde wrote:
Would changing (:tree path) so it accepts an optional argument be less
adhoc?
Possibly (:tree path key (depth nil)
(don-not-recure-after-asdf-encountered nil))
That said this would have little if
Faré wrote:
I did something much simpler: I enumerated the directories instead of
just loading the whole tree. My current settting is:
export CL_SOURCE_REGISTRY =
${sourceDirectory}/:${sourceDirectory}/uiop/:${sourceDirectory}/ext//:
That gets only ASDF, UIOP, and the dependencies.
I saw
On Aug 26, 2014, at 2:40 PM, Faré fah...@gmail.com wrote:
* a :source-registry entry can have a :cache entry (or be followed by
a :cache entry? or have a .cache file equivalent?) that lists all
relevant .asd files as a sorted list of relative unix-namestrings.
* Some script can regenerate the
I saw that. This doesn't help when asdf is in the source-registry,
though (which is the recommended way of having an asdf upgrade: just
having its source in the source-registry, e.g. in ~/common-lisp/asdf/)
Hm. And we have to have the asdf *tree* in the source-registry instead
of only
10 matches
Mail list logo
