Working with remote code

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...
>> Given the options, I would probably prefer not to use a samba share.
>> Stuff like compiling, etc are always much slower on a network share. I
>> realize you probably don't have that specific bit, but potentially your
>> editor, or syntax highlighting or whatever would then have to read
>> network files to find context. Nicer to have it locally, IMO.
> 
> Well, as I mentioned, some things need to be done on the remote server.  E.g. 
> most of the developers here work on systems written in Progress ABL, for 
> various reasons (both licensing and technical) we can compile and test that 
> code only on the server.
> 
> I see your point about the editor/IDE, etc having to read files over network.  
> To be honest that was my main issue with this approach as well.  The server is 
> local to our office though so maybe it wouldn't be a big issue.
> 
>> John
>> =:->
>>
> 
> Thanks for your comments, there's still some time before we start reorganizing 
> things, so I'll probably try out few approaches and see what works.
> 
> Cheers,
> Michael
> 
> 

When I tried it, I was running on a local 100Mb LAN, and compiling a
modest sized project. IIRC it took 1.5 => 2x longer to compile. Perhaps
if I had tried harder to make the build byproducts local?

Anyway, if you use 'bzr co $REMOTE' then every time you 'bzr commit' it
automatically is mirrored to $REMOTE. It is actually slightly stronger,
in that it will prevent the commit if you are out of sync with the
remote branch.

The one thing it won't do *today* is to auto-update the remote branch.
However you could write a post-commit or a 'post_change_branch_tip' hook
that would update the remote branch for you. So at least the manual
steps of updating stuff is reduced.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuH2w4ACgkQJdeBCYSNAAMQFwCfSm3G8HfiXO1Zqrn61zEgs3OU
I6YAnAilTEHxOSeuxqRvzB6M5/9OhGZL
=kGPY
-----END PGP SIGNATURE-----