-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Curtis Olson wrote:
> On Nov 29, 2007 9:33 AM, Melchior FRANZ <> wrote:
>> And it keeps two instances of every single file. That makes
>> 2 GB for all aircraft, rather than CVS' 1 GB. It's easy to
>> be quicker at updating, with this "little" help. And SVN
>> uses around 120% of the CPU while doing so. You can't do
>> much else with the computer at that time.
True, svn would work well for source, but not for data...
> 
> 
> The flip side of this is that our current rate of growth is not sustainable
> on the current server.  I am probably going to need to do something about
> that sooner rather than later.  I may have to find a new physical location
> for the flightgear cvs and ftp servers in the next few months as well.
> These are pretty high bandwidth machines, so running them off my home dsl
> connection is not a good solution for anyone.  I also need/want ssh access
> to the cvs server so I can do low level cvs maintenance and configuration
> when needed.
Anyone considered some distributed version control system like mercurial? Unlike
git, mercurial is quite easy to learn.

git got too many different commands and is confusing even for people used to
other distributed version control systems IMO. I used bzr first, and could adapt
to mercurial quite easily, still haven't managed to use git well, after several
months... Even darcs was easier to get used to.

> 
> Question about svn: I haven't looked closely at it.  How does it handle
> authentication and write access?  Is it similar to cvs where it leverages
> the host's user account and file system permission system, or does it have
> it's own built in scheme?  I.e. if we did switch to svn, would we still need
> to create unix accounts and manage unix permissions to control write access
> to the repository?
I'm not sure about that, considering that the repo format on server does not
support unix permission control at more than repo level... However with
committing by mod_svn (over https) I think what you want is supported by a
config file in recent svn versions, not sure about details.
> 
> Regards,
> 
> Curt.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFHTvhXWmK6ng/aMNkRCo/2AKDGbo6fLTrbjV1WIWlLnYfAO68wDgCdGtVY
M3Hwo/W0WiCs3ngI+wIpwxY=
=bOJp
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to