8,602
edits
FlightGear Git: splitting FGData: Difference between revisions
Jump to navigation
Jump to search
m
FlightGear Git: splitting FGData (view source)
Revision as of 13:23, 16 October 2011
, 16 October 2011no edit summary
mNo edit summary |
|||
| Line 1: | Line 1: | ||
[[Aircraft]] are split to seperate [[Git]] repositories, under the [https://gitorious.org/flightgear-aircraft FlightGear Aircraft] project at Gitorious. | [[Aircraft]] are split to seperate [[Git]] repositories, under the [https://gitorious.org/flightgear-aircraft FlightGear Aircraft] project at Gitorious. | ||
== Reasons to split fgdata == | |||
* '''Advantages''' | |||
** Aircraft authors can get commit access to their own aircraft, without granting them global fgdata access. | |||
** When pulling fgdata, one won't have to download several gigs of aircraft data. People will have to pull the base package, but any additional aircraft will be optional. | |||
* '''Disadvantages''' | |||
** It will be harder to keep a local up to date copy of all aircraft. No more "git pull" to fetch all the latest updates. | |||
*** Might be fixed by using Git submodules.<ref>[http://book.git-scm.com/5_submodules.html Git Community Book: Submoduldes]</ref> | |||
== Starting new aircraft == | == Starting new aircraft == | ||
| Line 17: | Line 25: | ||
cd fgdata | cd fgdata | ||
git subtree split -P Aircraft/737-300 -b 737-300 | git subtree split -P Aircraft/737-300 -b 737-300 | ||
mkdir ../split-aircraft/737-300 | |||
cd ../split-aircraft/737-300 | cd ../split-aircraft/737-300 | ||
git init | git init | ||
| Line 32: | Line 41: | ||
git reflog expire --expire=now --all | git reflog expire --expire=now --all | ||
git gc --aggressive --prune=now | git gc --aggressive --prune=now | ||
{{Appendix}} | |||