<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 11/20/2011 12:59 PM, Juan Jose Garcia-Ripoll wrote:
<blockquote
cite="mid:CANejTzp1HwOaF9zNGnHreuzV+mh3+Gj8r8Hm4mugw3Wihivh2Q@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Sun, Nov 20, 2011 at 9:16 PM, Paul
Bowyer <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:pbowyer@olynet.com">pbowyer@olynet.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
Since I already have quicklisp installed and it's accessible
from slime, or via clbuild using a command shell, it would be
redundant to have it (re-)installed by the ECL test suite
unless it was isolated to the ecl-test folder.</blockquote>
</div>
<br>
It seems I am not able to reach you guys, so I will try to explain
it more clearly. There are two different goals:
<div>
<br>
</div>
<div>1) Just testing ECL for ANSI compliance</div>
<div><br>
</div>
<div>2) Testing running of libraries with <br clear="all">
<div><br>
</div>
<div>The first goal is no problem: one just has to download the
tests and run them. I want to automate and make this as
painless as possible. It cannot be that in order to test
whether ECL built properly the user has to download and
install SVN (I think I discussed this in the ANSI-test mailing
list without success in the past). If possible, this should be
integrated into ECL's tree, for it would take eventually no
space: almost all the tests are in the ANSI test suite. Having
a library that allows downloading files via http and creating
a simple mirroring software that uploads copies of the test
suite to sourceforge would make this very easy to use and
straightforward to implement.</div>
<div><br>
</div>
<div>The second goal is <b>not compulsory</b>. Not even
supportive users are expected to do it regularly, but I may
ask a user to do it when a copy of ECL behaves strangely. In
any case testing of libraries can never be done using the
user's existing environment. For a simple reason: his
configuration may affect the tests, as it has happened in the
past (*). So I am not going to force you to download quicklisp
again, but I am not going to integrate testing of quicklisp
libraries using the copies you have downloaded. This has to be
done in a clean environment, with a fresh new copy of the
system.</div>
<div><br>
</div>
<div>Incidentally, I am trying to migrate my whole testing
environment to a standalone library that would control both
actual machines and virtual machines, performing tasks such as
starting virtual machines, monitoring them, uploading
distributions and tests, building them and retrieving and
parsing the results. This is yet another motivation to
integrate the build and the tests in a simpler way, free of
dependencies.</div>
<div><br>
</div>
<div>Juanjo</div>
<div><br>
</div>
<div>(*) For instance, ASDF looks for libraries all over your
computer by default. This makes existing or forgotten copies
of libraries interfere with quicklisps. That includes users's
projects and it has happened in the past. Other
customizations, such as ~/.eclrc files also interfere as they
change the build environment.</div>
<div><br>
</div>
-- <br>
Instituto de Física Fundamental, CSIC<br>
c/ Serrano, 113b, Madrid 28006 (Spain) <br>
<a moz-do-not-send="true"
href="http://juanjose.garciaripoll.googlepages.com"
target="_blank">http://juanjose.garciaripoll.googlepages.com</a><br>
</div>
</blockquote>
Juanjo:<br>
<br>
I apologize for not understanding your previous message on this
topic. Now that I more clearly understand your reasoning, I see no
problems with it.<br>
<br>
I'll go quietly back to learning to work with ECL...<br>
<br>
Paul<br>
<br>
</body>
</html>