[crossfire] crossfire source code control systems

Alex Schultz alex_sch at telus.net
Tue Aug 22 02:11:23 CDT 2006


Mark Wedel wrote:
> Mercurial: If a good hosting service is available, this may be the best option. 
>   But hosting here is tricky - commits, at current time, seem to need ssh access 
> (may change to https in the future).
>   
One note on this, as of Mercurial 0.9.1, you can push via http as well,
and for that one uses apache's http authentication to control access, so
it can run as pure CGI on a web server without even the ssh need. https
is also supported in the same way, provided the web server supports it.
> BZR: <snip> 
> The other issue is that it needs to make a new http connection for each file to 
> pull.  This may not be that big an issue for the server component (where there 
> are not a lot of files), but this could make things really slow for arch or maps 
> updates.
Well, it's a reasonably big issue on the server anyways, it takes about
2 hours (see one of Lalo's messages) to branch the crossfire server over
http with bzr. (of course, if one can handle that wait one time, it
isn't so bad after if one keeps an 'incoming' branch due to never having
to download the whole history ever again)

Alex Schultz



More information about the crossfire mailing list