371
edits
FlightGear Git: splitting FGData: Difference between revisions
Jump to navigation
Jump to search
m
FlightGear Git: splitting FGData (view source)
Revision as of 22:41, 19 October 2011
, 19 October 2011→Reasons to split fgdata
| Line 11: | Line 11: | ||
** 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. | ** 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> | *** Might be fixed by using Git submodules.<ref>[http://book.git-scm.com/5_submodules.html Git Community Book: Submoduldes]</ref> | ||
** How to deal with licences? Until now there was a COPYING file in fgdata. When aircraft are split in | ** How to deal with licences? Until now there was a COPYING file in fgdata. When aircraft are split in separate repositories, they'll likely need to include a license reference themselves. | ||
** Need a concept for release management, maintaining version numbers, release branches, release tags et. al. | ** Need a concept for release management, maintaining version numbers, release branches, release tags et. al. | ||