<div>Hi there,</div>
<div> </div>
<div>I recently had some trouble installing some planet packages so I wrote some scheme code to scrape the planet web page and install each package from scratch. The results can be seen at:</div>
<div> </div>
<div><a href="http://rivendell.ws/planet-stats/">http://rivendell.ws/planet-stats/</a></div>
<div> </div>
<div>It might not be a bad idea to incorporate this kind of automated testing into planet, perhaps by asking contributors to standardize on a testing procedure. But anyway,</div>
<div>of the 50 packags on planet, these 12 fail to install cleanly:</div>
<div><br>aspect-scheme<br>classic-java<br>java<br>macro<br>mrmathematica<br>namespace<br>port<br>redex<br>sql-oo<br>sqlite<br>xxexpr<br>yppdb</div>
<div> </div>
<div>I think a bug in the managed compilation library (lib "cm.ss") explains the problems with:</div>
<div> </div>
<div>aspect-scheme (maybe)</div>
<div>classic-java</div>
<div>sql-oo</div>
<div>sql-lite</div>
<div>xxexpr</div>
<div>macro</div>
<div>namespace</div>
<div>port</div>
<div> </div>
<div>I did not investigate the others very closely. The managed compilation problem can be reproduced by running the code below on a Windows box, inside the schemeunit cache directory created by the failed planet install (first delete everything from compiled):
</div>
<div> </div>
<div>
<p>(require (lib "cm.ss"))</p>
<p>(for-each (lambda (f)<br> (managed-compile-zo f))<br> '("assert-base.ss"<br> "assert-test.ss"<br> "assert-util-test.ss"<br> "assert-util.ss
"<br> "assert.ss"<br> "drscheme-ui.ss"<br> "graphical-ui.ss"<br> "keyword-test.ss"<br> "keyword.ss"<br> "
schemeunit.ss"<br> "test-test.ss"<br> "test.ss"<br> "text-ui.ss"<br> "util-test.ss"<br> "util.ss"))</p>
<p>-pp</p>
<p> </p></div>