On Sun, Mar 14, 2010 at 1:36 AM, Faré fah...@gmail.com wrote:
1- you want an ASDF operation that dumps some description of
things to be loaded.
2- you want to use a .asd itself as the output of that operation.
3- you want some location-independence in that description.
I presume the role
good evening;
On 2010-03-11, at 15:37 , Robert Goldman wrote:
If this gets loaded into the asdf git repo, I'll test on ACL linux
and Mac. Might manage windows, too
not yet in the asdf repo, but now reformulated to follow faré's
advise in recent correspondence:
On 3/13/10 Mar 13 -4:56 PM, Faré wrote:
I agree that ASDF 1.634 has reached the state of an ASDF 2 candidate,
at least codewise if not documentationwise.
If no one objects, I'm OK with enabling #+asdf2.
Want me to do it, or can you do it and release?
Done.
Cheers,
r
[ François-René
On 3/13/10 Mar 13 -7:36 PM, Faré wrote:
On 13 March 2010 16:56, Robert Goldman rpgold...@sift.info wrote:
On 3/13/10 Mar 13 -1:12 PM, Faré wrote:
We could adopt the same algorithm as dpkg or rpm uses for comparing version.
I once implemented it in shell script. Could do it in Lisp...
I
On 14 March 2010 04:21, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
No, interchangeability means not chance of using the library as it was used.
Not having it means that new ways of loading code and linking it into
executables of libraries should be found. New functions,
On 2010-03-15, at 01:36 , Faré wrote:
Dear James,
is there a tarball I can download with enough stuff to replace those
tests or yours?
?
the tests are all in the one asdf-pathname-test.lisp file.
I don't understand which cases exactly fail on which implementations.
the respective
