Ok, before I get flamed to a crisp, let me explain what is my reasoning behind
this. Right now the fgdata repository is about 9 GB. This makes it really,
really difficult to obtain an initial checkout of the fgdata folder, expecially
for people that do not have a very good connection. at the same time it is not
possible, to my knowledge, to only grab part of the repository. And most people
don't really need he entire repository anyway. GIT is fantastic to handle code
with many contributors, but I think it is really overkill for airplanes, where
usually the number of people contributing to a single plane is fairly small and
is unlikely that two people should work on the same file at the same time.
Also, using SVN for planes the same way that is being used for scenery would
allow individual planes to be pulled by a frontend, much like scenery is. Or
even to be pulled by FGFS itself, though that's probably science fiction at
this moment in time. So, is this something that could be implemented in the
future? Am I barking up the wrong tree? I can foresee some issues, like, where
should the repository be hosted, any other thing I have overlooked?
Waiting for comments, flames and people asking "who is this guy?", yours
sincerely,
Alessandro Garosi (aka Brandano on IRC)
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
