DrScheme always chooses only the most recent version of a PLaneT package by default when looking for tools to run at startup.<br><br>(Sorry I missed this message until now!)<br><br>-jacob<br><br><div><span class="gmail_quote">
On 1/22/07, <b class="gmail_sendername">Danny Yoo</b> <<a href="mailto:dyoo@hkn.eecs.berkeley.edu">dyoo@hkn.eecs.berkeley.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi everyone,<br><br>I'm planning to make a point release of DivaScheme to push another few bug<br>fixes we've made recently. (As well as a feature to cooperate with<br>DrScheme's automatic open-paren fixup thing. Hurrah!)
<br><br>One thing I was wondering, though: how does DrScheme choose which version<br>of a PLaneT-distributed tool to load?<br><br>Assuming that there are several versions of that tool already installed in<br>the local cache, does DrScheme always go for the highest version for each
<br>tool, or does it instead choose the one most-recently configured by<br>setup-plt?<br><br>I'm concerned that for people who already have DivaScheme (PLaneT package<br>1.0) release installed, the presence of that old version might interfere
<br>with any new releases. Regardless, it should be easy to address: I can<br>just write a quick uninstaller program that tells PLaneT to wipe older<br>versions of DivaScheme. Still, I'm curious what the official policy of
<br>this is.<br><br><br>Thanks!<br>_________________________________________________<br> For list-related administrative tasks:<br> <a href="http://list.cs.brown.edu/mailman/listinfo/plt-scheme">http://list.cs.brown.edu/mailman/listinfo/plt-scheme
</a><br></blockquote></div><br>