Just a quick update. I now run racket pointing to a main collects dir with only .zo files. It is working quite well!<div><br></div><div>Now I'm eyeing Jay McCarthy's archive code ;)<br><br><div class="gmail_quote"> On Tue, Oct 16, 2012 at 12:23 PM, 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"> <div class="im">At Tue, 16 Oct 2012 14:04:32 -0500, Robby Findler wrote:<br> > Besides what Eli says, another approach is to run 'raco setup -Dxi'<br> > after getting things out of perforce. That uses hashes for the files<br> > to determine what to compile (so nothing will get compiled if the zos<br> > are actually right), but it updates the timestamps (so racket won't<br> > get confused).<br> <br> </div>I think that's a good option.<br> <br> I think it's fine to omit ".rkt" files and ".dep" files, in which case<br> timestamps on ".zo" files don't matter.<br> <br> (You could also keep ".dep" files along with ".zo" files, in which case<br> timestamps still don't matter, but that doesn't seem useful.)<br> <br> </blockquote></div><br><br clear="all"><div><br></div>-- <br>Dan Liebgold [<a href="mailto:dan.liebgold@gmail.com">dan.liebgold@gmail.com</a>]<br> </div>