[racket-dev] module mismatch with .zos

From: Dan Liebgold (dan.liebgold at gmail.com)
Date: Tue Oct 16 15:33:03 EDT 2012

To be clear, we don't have any steps between sync in perforce and running
racket. This is for "end" users who don't edit or compile source. It is
also part of a toolchain where Racket is just one optional piece and so we
can't really spare the time to build zos at this particular point. We
really do need to distribute a package that is ready to run.

Perforce is our method for distributing a lot of other stuff already so
adding a new method is not trivial. Storing things centrally is a nice
approach but as I brought up in my last thread it is prohibitively slow.

It's sounding like my best approach is to put together a collects path that
contains just .zo files and also put together some sort of build automation
to create that tree. That would arrange updating and distribution that
would fit in our environment. (and if that tree could be archived into 1 or
few file(s) I'd be in hog heaven)

Thank you guys for your time and effort on this.


On Tue, Oct 16, 2012 at 12:23 PM, Matthew Flatt <mflatt at cs.utah.edu> wrote:

> At Tue, 16 Oct 2012 14:04:32 -0500, Robby Findler wrote:
> > Besides what Eli says, another approach is to run 'raco setup -Dxi'
> > after getting things out of perforce. That uses hashes for the files
> > to determine what to compile (so nothing will get compiled if the zos
> > are actually right), but it updates the timestamps (so racket won't
> > get confused).
> I think that's a good option.
> I think it's fine to omit ".rkt" files and ".dep" files, in which case
> timestamps on ".zo" files don't matter.
> (You could also keep ".dep" files along with ".zo" files, in which case
> timestamps still don't matter, but that doesn't seem useful.)

Dan Liebgold    [dan.liebgold at gmail.com]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/dev/archive/attachments/20121016/3e552fad/attachment-0001.html>

Posted on the dev mailing list.