<div dir="ltr">Ok, that seems to be exactly what I'm looking for -- however I tried it and it eventually seems to wind up using just the "compiled" path during raco setup.<div><br></div><div>Example output is here (I've echoed PLTCOMPILEDROOTS at the top, and note this is under windows): <a href="http://pasterack.org/pastes/45913">http://pasterack.org/pastes/45913</a></div><div><br></div><div>Is that enough context to see the issue?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 6, 2015 at 11:58 AM, Matthew Flatt <span dir="ltr"><<a href="mailto:mflatt@cs.utah.edu" target="_blank">mflatt@cs.utah.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">At Tue, 06 Jan 2015 14:14:22 -0500, Neil Van Dyke wrote:<br>
> Dan Liebgold wrote on 01/06/2015 02:00 PM:<br>
> > What is a straightforward way to designate the "compiled" directory to<br>
> > look for zo files in that can be based on the Racket version? I'd<br>
> > like to have Racket 5.2.1 and 6.1 running in parallel to aid in<br>
> > upgrading our version.<br>
> > Thanks!<br>
><br>
> I'd like for this to be the default behavior for Racket.<br>
><br>
> One possible way: Insert a directory level between the `compiled`<br>
> directory and its contents, with the directory named with the Racket<br>
> version number with which the code is compiled. Only that Racket<br>
> version will run that compiled code.<br>
<br>
</span>Although it's not the default, you can get that behavior by setting the<br>
`PLTCOMPILEDROOTS` environment variable to<br>
<br>
compiled/@(version):<br>
<br>
The trailing ":" allows compiled files to be found in "compiled" in the<br>
installation, while newly generated ".zo" files are put in a<br>
version-specific subdirectory.<br>
<br>
See also<br>
<br>
<a href="http://lists.racket-lang.org/dev/archive/2012-September/010386.html" target="_blank">http://lists.racket-lang.org/dev/archive/2012-September/010386.html</a><br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Dan Liebgold [<a href="mailto:dan.liebgold@gmail.com">dan.liebgold@gmail.com</a>]</div>
</div>