Dear ASDF maintainers,
would it be OK to apply the attached diff to asdf in git? It creates a
trivial build.xcvb and a trivial module definition for ASDF, so that
ASDF can be included in builds that use XCVB (including a bootstrapped
version of XCVB itself).
[ François-René ÐVB Rideau | Reflectio
nethics | http://fare.tunes.org ]
Instead of loving your enemies, treat your friends a little better.
-- Edgar Watson Howe
-- Forwarded message --
From: Sam Steingold
Date: 2009/7/8
Subject: Re: can't compile-file then load asdf.lisp
To: Faré
Cc: clisp-l...@lists.sou
2009/7/9 Gary King :
>> If something along the lines is put it, I would suggest that TRT is to
>> signal an error and offer restarts to either delete the package or
>> continue blindly.
>
> I agree and it seems that a named restart would allow XCVB function
> correctly, right?
>
No it wouldn't, and
2009/7/10 Stelian Ionescu :
> On Tue, 2009-07-07 at 12:31 +0200, Tobias C. Rittweiler wrote:
>> I think it's bitten pretty much all of us that we at least once tried to
>> push a non-directory-designating filename to *CENTRAL-REGISTRY*.
>>
>> It's a common pitfalls for newcomers.
>>
>> Couldn't ASD
Thanks a lot!
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
You cannot teach a man anything; you can only help him find it for himself.
-- attributed to Galileo Galilei
2009/7/12 Gary King :
> (cc'd to list)
>
> Hi Faré,
>
> My
Sorry to parasite this mailing-list, but I'm trying to design the
testing aspect of XCVB right now. The constraint is that we want to be
able to use make as a backend, and that test results should thus be
reified as files if we want to avoid re-running already-computed
tests.
My dim ideas about it
The default for ASDF's *central-registry* in SBCL contains a
(let (...) (when ...))
which can and *will* return NIL in some cases (i.e. when an executable
SBCL image is run).
On the other hand, sysdef-central-registry-search calls
directory-pathname-p on each entry, which assumes that
NIL is an
For years now, we at ITA have been satisfied with a patch that does
the following while building QRes: allow to specify module names that
include a directory component, without having to redundantly as in
(:module "subdir1/subdir2"
:components ((:file "subdir3/name3") (:file "subdir4/name4.subn
.tunes.org ]
To have a right to do a thing is not at all the same
as to be right in doing it. -- G.K. Chesterton
2009/8/28 Faré :
> For years now, we at ITA have been satisfied with a patch that does
> the following while building QRes: allow to specify module names that
> inclu
>> (loop for data = rest then (cddr data)
>> while data
>> for key = (first data)
>> for value = (second data)
>> ...)
What about
(loop :for (key value) :on data :by #'cddr
...)
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
The fear o
Uh? Whoever uses git to access asdf source code ipso facto has access
to a chunk of non-trivial unix software, and can be assumed to be able
to run a script. For instance,
one that appends (SETF ASDF::*REVISION* "1.362-2-g07f9837") to
asdf.lisp before it is copied over to its installation path, or
Note that I have been maintaining my variant of A-B-L as part of cl-launch,
and upon noticing that resolve-symlinks had been removed, I immediately
issued a new release 2.23 of cl-launch.
I for one would welcome A-B-L becoming part of ASDF, so I could have
cl-launch just use that (after a transiti
2009/9/9 Gary King :
> This release restores the `resolve-symlinks` function which I had
> removed while cleaning up without realizing that ASDF-Binary-Locations
> made use of it. Thanks to Robert Goldman for the catch.
>
Nope. Once again you must have committed to a branch.
Also, what's the statu
Oops. The header was boiler-plate from a QRes-specific file inside
which this patch was initially, and was never updated when the
ASDF-specific code was extracted. This is all free software under the
same license as ASDF. If you credit me in a git message, please use my
ITA address f...@itasoftware
I *think* that the following should work:
git push --tags $url master:master
Please double check.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
If debugging is the process of removing bugs,
then programming must be the process of putting them in.
-- Dijk
See attached file.
It would be nice if there were a "precheckin" test for ASDF.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Never explain. Your friends do not need it and your enemies will
never believe you anyway.
-- Elbert Hubbard
From 29239283483c1783
will make it more blatant.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
He who says he will die for a cause will probably lie for it and may kill
for it. -- John McCarthy
2009/9/12 Gary King :
> Hi Faré,
>
> I was incorporating your patc
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
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
CL software management
systems, unlike an ASDF-specific ASDF_PATH.
> As Faré pointed out, these should be specified through a site-specific
> configuration rather than being hard-coded into ASDF. Such configuration
> might involve querying an environment variable or reading a config file fro
2009/10/5 Robert Goldman :
> Alternatively, is it possible to modify the portable ASDF distro so that
> out of the box it would be capable of not breaking contrib modules?
>
I did my best in /xcvb/no-asdf to allow the uninstallation of a previous ASDF
such that the new installation will not break c
Maybe ASDF is the wrong place to try to standardize testing infrastructure?
I mean, maybe instead the authors of various test infrastructures
should have a common list where they discuss interoperability,
reporting, and a declarative way of specifying dependencies between
test suites, between file
Gary obviously doesn't have enough time to maintain ASDF and commit
(or reject) patches as fast as they come.
Gary, would you mind nominating other maintainers? If no one else is
eager to do it, I'm willing to commit bug fixes when they come. ("New"
features like TEST-OP and DOC-OP or whatnot I'll
While developing XCVB, I was reminded that when you declaim or
compile-toplevel proclaim optimization settings, these settings may
(ccl, allegro) or may not (cmucl, sbcl) persist beyond the compilation
of the current file. To make the build deterministic, XCVB now resets
the settings before every o
I ran the tests for asdf. Out of 17, 5 fail on sbcl and 7 on clisp. Oops.
On SBCL, the failures seem related to the pathname redirection of ABL / CLC.
test1.script test2.script test3.script test-force.script
test-static-and-serial.script
On CLISP, the two additional failures are
test-module-pathn
The cCLan list has apparently become the asdf-devel list.
Is this still where the upstream for split-sequence is? If so, can
this patch be applied? If not, who's in charge?
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
"Politics" is made up of two words, "Poli", w
; the others only fail on one.
>
> I'll check it out.
>
>
> On Oct 22, 2009, at 12:28 PM, Faré wrote:
>
>> I ran the tests for asdf. Out of 17, 5 fail on sbcl and 7 on clisp. Oops.
>>
>> On SBCL, the failures seem related to the pathname redirection of ABL /
>&
2009/10/23 Christophe Rhodes :
> Faré writes:
>
>> The cCLan list has apparently become the asdf-devel list.
>>
>> Is this still where the upstream for split-sequence is? If so, can
>> this patch be applied? If not, who's in charge?
>
> I guess I
2009/10/23 Tobias C. Rittweiler :
>> > >
>> > > +#+xcvb (module ())
>> > > +
>> >
>> > This is... no. Please find some way of not infesting code with
>> > build-related metainformation.
>> >
>> OK, I'll put this much-requested feature near the top of my TODO list.
>
> If every .lisp file has to be
2009/10/26 Tamas Papp :
> Hi,
>
> Suppose I have a library named MYLIBRARY which was installed in the
> directory /somewhere/foo/ (eg by ASDF-Install, clbuild or manually by
> the user). It has a /somewhere/foo/mylibrary.asd definition file,
> which was duly symlinked to mylibrary.asd in ASDF's ce
The recommended way is to write a trivial .asd file for said library.
The other way is to load this library first thing in your build as
part of your Lisp setup, the same that loads asdf.lisp itself and
configures your central registry and defines your optimization
settings.
Speaking of optimizat
2009/10/28 Gary King :
>> Speaking of optimization settings, does anyone see any problem with
>> putting in ASDF something that deterministically (re)sets the
>> optimization setting before each and any perform operation? Otherwise,
>> optimization settings will vary wildly depending on what
>> imp
2009/10/28 Robert Goldman :
> Faré wrote:
>> 2009/10/28 Gary King :
>>>> Speaking of optimization settings, does anyone see any problem with
>>>> putting in ASDF something that deterministically (re)sets the
>>>> optimization setting bef
(Moving the discussion from the ecl list to the asdf list,
originally Re: ECL support for cl-launch and xcvb)
2009/11/9 Juan Jose Garcia-Ripoll :
>> For the record, the issue I finally found and fixed in building an
>> image was as follows: asdf:traverse is traversing system dependencies
>
> I hav
2009/11/10 Robert Goldman :
> An additional problem is that there is no clear relationship between the
> ASDF project and the versions of ASDF shipped with implementations.
>
> I find that this is a strong disincentive for me to work on even
> backwards-compatible extensions to ASDF (asdf extension
Looks great!
With such minimal and innocuous changes to asdf.lisp itself, I think
applying the patch upstream should be a no-brainer. That said, I don't
have commit access.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
When all lawful citizens are disarmed, will w
I volunteer for the commit bit. I won't do anything far-fetching with
ASDF, but I will
* merge the ECL patch
* accept contribs outside of asdf.lisp itself (e.g. for TEST-OP and DOC-OP).
* try to improve ASDF:
* make it use a configuration file https://bugs.launchpad.net/asdf/+bug/485918
* make
Dear ASDF developers,
I've committed to *a new repo* a few ASDF hacks that I wrote. I'd like
some of you to review and/or test it. I'd like to get it reviewed
before I push those changes to the official repo.
git clone http://common-lisp.net/project/xcvb/git/asdf.git
cd asdf
git diff -u -a -b 1f7
Beside running tests with SBCL, what is the release process for ASDF?
Are there a script to automatically increase the revision number,
commit, build tarballs, update online documentation?
The bin/ directory suggests there are, but it's unclear what is the
correct usage pattern (if any), and I'd
2009/12/1 Juan Jose Garcia-Ripoll :
> On Mon, Nov 30, 2009 at 10:17 PM, Faré wrote:
>
>> Known issues (juanjo, help appreciated):
>>
>> $ ecl -eval "(require :asdf)" -load "asdf.lisp" ==> works
>> $ ecl -eval "(require :a
ompile asdf.fas with debugging
information. How do I do that?
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Success is getting what you want. Happiness is wanting what you get.
-- Dale Carnegie
2009/12/1 Juan Jose Garcia-Ripoll :
> On Tue, Dec 1,
2009/12/1 Robert Goldman :
> I just checked, and I see that my documentation patches have not been
> pushed. Any objection to pushing them before the release?
>
> If you are willing to do that, I'd appreciate it. I prefer not to do
> anything irrevocable to the git repo
>
Sure. Those of you w
2009/12/1 Robert Goldman :
>> Sure. Those of you who have patches you want included in the next
>> release, please re-send them to me, if possible based on my
>> development repo at
>> http://common-lisp.net/project/xcvb/git/asdf.git
>
> OK, I will resend.
>
I got two small documentation patches
2009/12/1 Juan Jose Garcia-Ripoll :
> On Tue, Dec 1, 2009 at 9:05 PM, Faré wrote:
>> I think that it is the very design of ASDF that a .asd file is Lisp
>> source code, and that we thus reuse Lisp as the language to do magic
>> there. What better way to load extensions i
2009/12/2 Robert Goldman :
> I should actually have been specific about something else:
>
> If we prefer spaces to tabs (and I will not attempt to stack my
> eloquence and vituperation against jwz's), we should probably stick the
> git-equivalent of a pre-commit-hook into the repo to refuse to acce
.asd sounds sufficient to me, but Gary wrote a lot of
> shell scripts I haven't really looked at. I don't have a strong
> opinion about the documentation source (perhaps surprisingly).
> Best,
> R
>
> On Dec 2, 2009, at 20:54, Daniel Herring wrote:
>
>> On Wed
Having had no feedback for a week, and passing tests, I decided I'd
push what I have so far to the official repository.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
___
asdf-devel mailing list
asdf-devel@common-lisp.net
ry government is evil doesn't mean "native"
governments have a right to exist and enslave "their" people. — Faré
___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
So... is anyone against my committing a release that just untabifies
all our Lisp files?
Speak up now, or remain silent forever.
On the other hand, if there's no way to enforce it, then it will
constantly diverge, so the policy becomes annoying.
[ François-René ÐVB Rideau | Reflection&Cybernethi
2009/12/18 Nikodemus Siivola :
> Some questions and notes:
>
> How do I instrospect *SOURCE-REGISTRY*? The outlined API only puts
> stuff there, but doesn't tell me how to read it.
>
For the moment, I don't have a good story for a public API on how to do that.
But considering that only ASDF and XCV
Tobias, do you want to have the commit bit, so you may check in fixes
to the bugs you reported?
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Government is a disease masquerading as its own cure.
— Robert LeFevre (1911 - 1986)
_
2009/12/18 Robert Goldman :
> In trying to dig at one of TCR's bugs, I was archaeologizing asdf.lisp,
> to figure out the contents of the *defined-systems* table. Put what I
> came up with into a docstring.
I committed it in my "development" repo at
http://common-lisp.net/project/xcvb/git/asdf
2009/12/19 Tobias C. Rittweiler :
>
> At the moment *ASDF-REVISION* is a DEFVAR which won't be reset on
> reloading. The attached patch makes it a DEFPARAMETER, so
> *ASDF-REVISION* will reflect the correct version after a self-upgrade.
Well spot. Applied to my "development" repo.
[ François-René
sh a valid, self-upgradable ASDF "once and for
all".
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
The main reason Santa is so jolly is because
he knows where all the bad girls live.
2009/12/19 Nikodemus Siivola :
> 2009/12/19 Faré :
>
>
2009/12/21 Samium Gromoff <_deepf...@feelingofgreen.ru>:
> Fare,
>
> Please consider the patch in the 'missing-definition' branch in
>
> git://git.feelingofgreen.ru/asdf
>
Applied in my development repo, master branch:
http://common-lisp.net/project/xcvb/git/asdf.git
Candidate for immediate r
2009/12/21 Tobias C. Rittweiler :
>> Applied in my development repo, master branch:
>>http://common-lisp.net/project/xcvb/git/asdf.git
>>
>> Candidate for immediate release, if no one else disagrees.
>
> (The above link is pretty useless.)
>
> What does the patch do?
>
This link might be more u
Seeing that ASDF hasn't changed much in the last few weeks, I released
1.375, which contains some documentation changes by Robert Goldman,
and a patch by Samium Gromoff.
Note once again that while willing to accept patches and release
promptly (or not so promptly, it seems, if you don't consider i
nd programming. — Faré
___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
I updated the code in my ASDF repository, did a second pass on the
configuration code.
I included some documentation in README.source-registry that probably
should be integrated in the "normal" ASDF documentation and/or in web
pages.
Can you look at it?
Is anyone interested in updating documentatio
2010/1/18 Robert Goldman :
>> http://common-lisp.net/gitweb?p=projects/xcvb/asdf.git
>> https://bugs.launchpad.net/asdf/+bug/485918
>>
>> This hooks into the asdf sysdef search mechanism in a way that takes
>> precedence over the current *central-registry* but falls back to it
>> when systems are n
Dear ASDF-interested hackers,
I've cleaned up my code for ASDF configuration and committed it to my repo.
http://common-lisp.net/gitweb?p=projects/xcvb/asdf.git
Documentation is currently in
README.source-registry
there.
While discussing with Peter Van Eynde and James Knight regarding
debia
If you actually send the backtrace on the list, or attach it to an
ASDF bug on launchpad.net, that would help a lot figure out what's
wrong and how to fix it.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
A computer is like an Old Testament god, with a lot of rules
2010/1/20 Nick Levine :
> From: =?ISO-8859-1?Q?Far=E9?=
> Date: Wed, 20 Jan 2010 14:30:48 -0500
> Cc: Nick Levine , asdf-devel@common-lisp.net
>
> If you actually send the backtrace on the list, or attach it to an
> ASDF bug on launchpad.net, that would help a lot figure out what's
> w
2010/1/20 Peter Van Eynde :
> instead of /etc/common-lisp/source-registry.conf I would like to see
> /etc/common-lisp/source-registry.conf.d
>
> where instead of having one file that you might have to edit in
> post-installation scripts we would have a directory where packages can
> just drop files
2010/1/20 Nick Levine :
> Your backtrace shows nothing obviously wrong, and if extending the
> stack does the trick, the problem is possibly that LW starts with
> an extremely small stack and/or does some stack-allocation
> optimizations that blow the little stack it has. I blame LW
> set
OK, the ASDF my repo now supports source-registry.conf.d as well as
source-registry.conf. I'll commit it upstream by next week unless I
get negative feedback, and hopefully after including some tests.
Note that at least clisp seems confused when matching *.* or
(make-pathname :type :wild :name :wi
Didn't apply to my development repo. Had to redo it by hand. Committed.
http://common-lisp.net/gitweb?p=projects/xcvb/asdf.git
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Have the courage to take your own thoughts seriously, for they will shape you.
I've just released ASDF 1.501 in the official repository, now with all
the source registry configuration that I previously discussed. It's
currently documented in its own file README.source-registry, rather
than in the general manual asdf.texinfo, as it should be. Patch
welcome.
Note that I bumped
10/1/27 Robert Goldman :
> On 1/27/10 Jan 27 -12:50 AM, Faré wrote:
>> I've just released ASDF 1.501 in the official repository, now with all
>> the source registry configuration that I previously discussed. It's
>> currently documented in its own file README.source-r
Applied manually to my tree. git am rejected it with "invalid email
address", even after I fixed the email address.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
They laughed at Columbus, they laughed at Fulton, they laughed at the
Wright brothers. But they also l
Using a development branch on the public repo sounds alright to me.
I started my repo before I had the commit bit on the public repo,
which is what got me started historically.
I didn't change my workflow just because I've been too lazy to learn
how to do it so far.
If someone will point me to a d
Oops, you're right. So here's ASDF 1.502.
Also includes a fix to bug 513338 (ccl support in test).
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Living your life is a task so difficult, it has never been attempted before.
On 30 January 2010 16:14, Peter Van Eynd
My plan for ASDF 1.600 is to rename the (recently) builtin
asdf-binary-locations to asdf-output-locations and make a few
incompatible changes to it.
* These changes will allow for configuration through an API similar to
the one I introduced for the source-registry in 1.500.
* I don't think many peo
Dear Tobias,
thanks for your feedback.
> a) I don't particularly like the name Output Locations. I can
> understand that a different name is needed. "FASL Location", would
> probably be most intuitive to Lispers -- though it can be used for
> more stuff.
But there's is more than FASL
is-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
May your desire to be correct overcome your desire to have been correct
(which you were not, anyway). — Faré
___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
On 1 February 2010 10:34, Robert Goldman wrote:
> Having the documentation here is helpful, but a few examples would be
> even more helpful.
>
> For example, if I wanted to replicate Gary's A-B-L in the new
> configuration language, how would I do that? I don't see an opportunity
> in the languag
>> Note that with ABL, you must carefully load ABL and set whichever
>> variable in each Lisp startup script, so the amount of work is no
>> less.
>
> I don't see this --- all I do is load it and I'm done, and it's not so
> carefully, either. It's just a one-liner. Your experience of A-B-L and
>
I agree with James that a bootstrapped asdf would be elegant.
Unhappily it wouldn't be practical. asdf being only one file is very
useful for many reasons. It being one directory would not be too bad,
but still one file is better. pjb has a nice suggestion that we could
split it in many files and h
Attila suggested that the ASDF output cache be enabled by default. I
think that's a good idea, but didn't dare propose it here because of
concerns with backwards compatibility.
Does anyone think we should keep the cache disabled by default?
Speak now, or remain silent forever!
[ François-René ÐV
>> I agree with James that a bootstrapped asdf would be elegant.
>> Unhappily it wouldn't be practical. asdf being only one file is very
>> useful for many reasons.
>
> please explain.
>
Distribution. Only one file to download and install anywhere, rather
than having to dig through a directory, mak
It's raw and unpolished, but on my repo is first attempt at an
asdf-output-translations.
If anyone cares to get a look and comment, or even test, there's great!
http://common-lisp.net/gitweb?p=projects/xcvb/asdf.git
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Th
>> Distribution. Only one file to download and install anywhere, rather
>> than having to dig through a directory, make sure things are there,
>> etc. So far, it has been a constraint respected by ASDF.
>
> if the requirement is, that the single asdf.lisp load stand-alone,
> the experiment i posted
Dear Daniel,
> My issue is that there is a great similarity; this similarity is driven by a
> need inherent in the use of libraries; but ASDF (due to history) has certain
> things absolutely backwards.
If you want to fix Lisp build tools in a way that is incompatible with
ASDF, then ASDF isn't it.
On 3 February 2010 11:32, Scott Bell wrote:
> (:group "x"
> :depends-on ("packages")
If you're not in a subdirectory #p"x/", here add a
:pathname #p""
> :components
> ((:file "a")
> (:file "b" :depends-on ("a"))
> (:file "c" :depends-on ("b"))
I just released ASDF 1.600 in the official repository.
Since my last "official release" 1.502, there is
* AOT replacing ABL. AOT allows you to define a set of pathname
translations in a configuration file.
* Some cleanup of the ECL integration.
* *asdf-revision* has been replaced by *asdf-version*
I applied your two other patches, but this one won't apply, probably
because of redundant whitespace changes.
Please merge it with the latest head on my repo.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Amateur bureaucrats are often even worse than professional
Committed as ASDF 1.601. Thanks!
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
There are two distinct classes of men in the Nation, those who pay taxes
and those who receive and live upon the taxes. — Thomas Paine
On 4 February 2010 01:36, Chun Tian (binghe) w
çois-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
You're currently going through a difficult transition period called "Life."
On 4 February 2010 03:04, Juan Jose Garcia-Ripoll
wrote:
> On Thu, Feb 4, 2010 at 1:23 AM, Faré wrote:
>>
>>
]
Due to circumstances beyond your control, you are master of your fate
and captain of your soul.
On 4 February 2010 04:10, Juan Jose Garcia-Ripoll
wrote:
> On Thu, Feb 4, 2010 at 9:23 AM, Faré wrote:
>>
>> And so, regarding ECL: please upgrade ASDF to 1.601 if you can. It
>
On 4 February 2010 12:08, Robert Goldman wrote:
> In the asdf/test directory
> perl -pi.bak -e 's|"../asdf"|\(compile-file-pathname "../asdf"\)|;' *.script
Done. Committed to my repo, but after I did a 1.602 release that fixes
more tests and fixes your bug about increased debuggability of tests.
Dear Juanjo,
I just released 1.602 that quashes more warnings with ECL and passes
more tests with more implementations, but it is functionally identical
to 1.601 or 1.596 (except for the addition of COMPILE-FILE-PATHNAME*).
ASDF didn't use to support ECL for testing at all. I just added this
supp
If it's the compile-asdf script hanging instead of exiting, I just
pushed 1.603 that has a fix for running tests in ECL w/o manual
intervention. My apologies. (No functional change to asdf itself, only
to the test script infrastructure.)
[ François-René ÐVB Rideau | Reflection&Cybernethics | http:
Dear Robert,
> However, there is no easy way to have a module update its components
> upon dependency change but not have a system update its components upon
> dependency change, because a system is a subclass of module.
thanks for your work and congratulations for fixing the bug!
> So my path m
needed. Thanks a lot!)
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
``why'' is always relative to a model of possible explanations. It is never
an "absolute" question. Which is precisely what makes it meaningful.
— Faré
___
On 10 February 2010 00:28, Robert Goldman wrote:
> I believe my first ASDF patch had a minor buglet that could cause
> over-compilation.
>
> Here's the deal: when new TRAVERSE detects that the components of a
> module need to have an operation performed on them, it binds a dynamic
> variable and
On 10 February 2010 18:27, Robert Goldman wrote:
> OK, I have just pushed an alternative solution to the module dependency
> bug, this one (I believe) only triggered by INTRA-system dependencies.
> This one is also on the module-depends branch.
>
A test! This requires a test case in the test suite
> I think to be fair to James he's not saying that ASDF should DWIM, he
> was asking for a minimum perturbation fix.
>
No, he's rejecting an actual fix to actually broken behaviour,
in favor of something that's not specified and not specifiable,
whereas anything meaningful and specifiable he could
On 12 February 2010 05:04, james anderson wrote:
> good morning;
>
> this commit[1] changes the declaration for *system-definition-search-
> functions* in order that an upgrade modify it.
> would it not be better to unbind it in the "hot-upgrade" section?
>
> ---
> [1]: http://common-lisp.net/gitw
>>: Faré
>: james anderson
>
>> Maybe the current timestamps in ASDF are somewhat lacking, but
>> that doesn't mean timestamps can't solve the issue. I think that
>> one timestamp per pair (op component) should do the trick, stored
>> as an alist (op
Thanks!
Shouldn't
(or *forcing*
(and
(not (typep c 'system)))
forced)
be instead
(or *forcing*
(and
(not (typep c 'system))
forced)
?
Need a test case for that. Sigh.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
The [classi
1 - 100 of 1924 matches
Mail list logo
