Just a quick update. I now run racket pointing to a main collects dir with
only .zo files. It is working quite well!
Now I'm eyeing Jay McCarthy's archive code ;)
On Tue, Oct 16, 2012 at 12:23 PM, Matthew Flatt wrote:
> At Tue, 16 Oct 2012 14:04:32 -0500, Robby Findler wrote:
> > Besides what E
On Tue, Oct 16, 2012 at 12:04 PM, Robby Findler wrote:
> (FWIW, it is not really wrong to consider this behavior a bug at a
> number of different levels (why rely on timestamps? why does
> compilation not produce the same thing each time?) and it is something
> we've struggled with for a long tim
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 d
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
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). This is p
A few minutes ago, Dan Liebgold wrote:
> It seems like the timestamps among just the .zo and .dep files will cause us
> issues as well due to how Perforce works. When you sync, Perforce sets the
> timestamp of the file to the time of sync. If I sync all of a Racket
> distribution my file timestamps
It seems like the timestamps among just the .zo and .dep files will cause
us issues as well due to how Perforce works. When you sync, Perforce sets
the timestamp of the file to the time of sync. If I sync all of a Racket
distribution my file timestamps will not be coherent from Racket's point of
vi
On Mon, Oct 15, 2012 at 7:59 PM, Dan Liebgold wrote:
> On Mon, Oct 15, 2012 at 5:23 PM, Matthew Flatt wrote:
>>
>> Is there any chance that the ".zo" file timestamps became earlier than
>> the ".rkt" timestamps on end-users' machines?
>>
>
> Yes that is possible... we're distributing using Perfor
On Mon, Oct 15, 2012 at 5:23 PM, Matthew Flatt wrote:
> Is there any chance that the ".zo" file timestamps became earlier than
> the ".rkt" timestamps on end-users' machines?
>
>
Yes that is possible... we're distributing using Perforce, which timestamps
files at the time of syncing. Would that g
Is there any chance that the ".zo" file timestamps became earlier than
the ".rkt" timestamps on end-users' machines?
Users are better off with the ".dep" files. I think `raco make' would
use them, for example.
At Mon, 15 Oct 2012 15:10:18 -0700, Dan Liebgold wrote:
> We're having trouble with .zo
10 matches
Mail list logo
