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.
Example output is here (I've echoed PLTCOMPILEDROOTS at the top, and note this is under windows): http://pasterack.org/pastes/45913 Is that enough context to see the issue? On Tue, Jan 6, 2015 at 11:58 AM, Matthew Flatt <mfl...@cs.utah.edu> wrote: > At Tue, 06 Jan 2015 14:14:22 -0500, Neil Van Dyke wrote: > > Dan Liebgold wrote on 01/06/2015 02:00 PM: > > > What is a straightforward way to designate the "compiled" directory to > > > look for zo files in that can be based on the Racket version? I'd > > > like to have Racket 5.2.1 and 6.1 running in parallel to aid in > > > upgrading our version. > > > Thanks! > > > > I'd like for this to be the default behavior for Racket. > > > > One possible way: Insert a directory level between the `compiled` > > directory and its contents, with the directory named with the Racket > > version number with which the code is compiled. Only that Racket > > version will run that compiled code. > > Although it's not the default, you can get that behavior by setting the > `PLTCOMPILEDROOTS` environment variable to > > compiled/@(version): > > The trailing ":" allows compiled files to be found in "compiled" in the > installation, while newly generated ".zo" files are put in a > version-specific subdirectory. > > See also > > http://lists.racket-lang.org/dev/archive/2012-September/010386.html > > -- Dan Liebgold [dan.liebg...@gmail.com]
_________________________ Racket Developers list: http://lists.racket-lang.org/dev