159
edits
FlightGear Git: splitting FGData: Difference between revisions
Jump to navigation
Jump to search
FlightGear Git: splitting FGData (view source)
Revision as of 15:41, 30 October 2011
, 30 October 2011→Reasons to split fgdata
| Line 7: | Line 7: | ||
** 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. NOTE: Can't reproduce even on really old, slow (7.2k SATA) disks. | ** 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 | ** fgdata size decreases from 5,6 GB to 1 GB (see statistics below). | ||
* '''Disadvantages''' | * '''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. | ** 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. | ||
| Line 15: | Line 15: | ||
** 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. | ** 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. | ** 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. | ||
* '''Statistics''': To obtain proper GIT repository size statistics, make sure to only check the size of the ".git" folder - which contains the history that belongs to the archive and needs to be downloaded. Once you check out a branch as a "working copy", the size of your actual file system folder increases (likely doubles), since the check-out creates a working ''copy'' of all files by ''extracting'' data from the ''compressed'' archive. | |||
** Size of original fgdata GIT repository: 5.6GB | |||
** Size of fgdata core GIT repository without aircraft: 1GB | |||
** Total size of all aircraft repositories: 3.1GB | |||
** Number of aircraft: 385 | |||
=== Reasons to put aircraft under a single project === | === Reasons to put aircraft under a single project === | ||