On Wed, Sep 2, 2009 at 2:02 PM, Tom P <zomm...@gmail.com> wrote:
> Hi Curt
>
> My only concern with SVN is that it stores every file twice in the local
> file system, so it's not ideal for the 'data' portion of FlightGear. For
> example, right now a complete checkout of Aircraft is ~ 2 GB, and it would
> double overnight.
>
A quick check of the 'data' repository reports it's size is about 5Gb.
Presumably with a distributed source code control system, each end user
would be downloading this much data + the disk space foot print would be at
least this much (+ maybe the extra 2Gb for a working copy?)
Is this an argument to stay with CVS for the data portion of the project?
This is a good point to bring up though in advance. The default project
quota at code.google.com (is there a shorter abbreviation?) is 1Gb so we'd
be fine for SimGear and FlightGear code, but we'd blow way over that for
data.
I know, disk space is cheap in these days, but the double-write also results
> in slower checkouts.
> In other words, I think we should import FlightGear as well into
> code.google.com and see if we are happy with the performance before
> jumping.
>
Part of the goal of my original post was to have people take a look at
SimGear in google/svn form to see if there were any major oversights in the
migration process before we make any actual move. But certainly the large
size of the data is an additional dimension to test.
> Apart from this concern, I've used CVS, SVN and GIT and I'm not religious
> about the choice.
> In the end, any tool will work as long as it's:
> - fast
> - easy to use
> - well integrated with other tools like bug tracking SW <----- and this
> is very important IMHO
> (you have bugs referring to check-ins, check-ins referring to bugs, RSS
> feeds of changes, etc ...)
>
I noticed google has an interesting system (which I haven't explored in
detail) that allows users to rate individual commits as positive, neutral,
or negative, with the option to leave comments. Any changes to the tools
also implies some changes to the typical workflow, but code.google.com has
some nice features. It also supports mercurial (hg) which might be an
option for the future if we decide a distributed source code management
system is the better way to go.
Regards,
Curt.
--
Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
