Kad bi 18:38:11, Michael rece:
>> We've missed something fundamental - there is no safety whatsoever in
>> re-rsyncing during a testing run. The rsync server may have moved on.
> Second problem, we're all smoking against different patch levels. To
> make this really effective, we should all work on the same one. I
> know there's some sort of daily snapshot lying around. Insted of
> rsyncing perl-current, we should probably download this. It'll also
> lose the dependency on rsync, which doesn't work on alot of OS's.
How about this approach:
rsync to one directory and build on another which is localy rsynced.
This would make things much faster, but would consume more space. Thats
about speed, but as I've tested, make distclean takes about 8-10
minutes, and rsyncing (from local copy) 6-7 minutes.
I don't think that downloading daily snapshot would work, at least for
me. Since I'm working on 14400 BPS modem, it would be sooooo slow. It's
better to rsync perl-current, but in particular time. Then we should
have the same patch-level.
No, forget it. It was nice idea if we are all in the same time zone...
this way some should awake in 4PM :>
--
. `\!,
. <. .>
[=======oOo==( ^ )==oOo========[ [EMAIL PROTECTED] ]=======]
|--- _ - --- [ member of ]--- |
[========( )======_==============[ .counter attack. ]==]
. () ( )
. ()
