116
edits
FlightGear Git: splitting FGData: Difference between revisions
Jump to navigation
Jump to search
FlightGear Git: splitting FGData (view source)
Revision as of 08:05, 20 October 2011
, 20 October 2011starter package
Martin.spott (talk | contribs) (starter package) |
|||
| Line 6: | Line 6: | ||
** 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. | ** 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. | ||
** It will be easier for aircraft authors to check the history of their aircraft. | ** It will be easier for aircraft authors to check the history of their aircraft. | ||
** Commiting will go faster, because Git will no longer have to check those thousands of files to see whether they were edited. | ** Commiting will go faster, because Git will no longer have to check those thousands of files to see whether they were edited. NOTE: Can't reproduce even on really old, slow (7.2k SATA) disks. | ||
** fgdata size decreased from 9,34 GB to 1,78 GB. | ** fgdata size decreased from 9,34 GB to 1,78 GB. | ||
* '''Disadvantages''' | * '''Disadvantages''' | ||
| Line 13: | Line 13: | ||
** 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. | ** 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. | ||
** Quite a few unmaintained aircraft got adopted after one of the developers accidentially tripped over them. Need a plan how this would be supposed to work with split aircraft repositories, otherwise the project would axe one of the substantial principles which contributed to its success. | |||
** Need an idea about how to subsitute the the previous "starter" package which was offered via HTTP for those who'd like to have the entire repository. | |||
=== Reasons to put aircraft under a single project === | === Reasons to put aircraft under a single project === | ||