Advertisement
Guest User

fgmembers wiki article

a guest
Apr 29th, 2016
216
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.83 KB | None | 0 0
  1.  
  2. '''FGMEMBERS''' is ...
  3.  
  4. * A Git repo of aircraft for FlightGear from various sources, using git sub modules
  5. * A group of aircraft and scenery developers and contributors on github
  6. * A fork of [[FGAddon]], which may also contain aircraft without explicit permission/support and collaboration from its original developers. An aircraft showing up in FGMEMBERS doesn't necessarily mean that the original developers endorse this.<ref>{{cite web |url=http://forum.flightgear.org/viewtopic.php?f=42&t=26043&hilit=parasitic&start=135#p241138 |title=Re: FGAddon vs. FGMEMBERS, bus factors etc. |author=IAHM-COL |date=Thu Apr 30, 2015 |publisher=FlightGear forum |accessdate=Fri Jun 12, 2015 }}</ref>
  7. * Initiated by a single contributor, [https://github.com/IAHM-COL IAHM-COL].
  8.  
  9. == Repositories ==
  10. The repositories are actually several repositories arranged under five groups. The groups split content into aircraft, scenery and other data as well as content published under the [[GNU General Public License]] (GNU GPL) or under other licenses.<ref>{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=231382#p231382 |title=Cloning fgdata with GIT submodules |author=IAHM-COL |date=Thu Feb 05, 2015 |publisher=FlightGear forum |accessdate=Fri Jun 12, 2015 }}</ref><ref>{{cite web |url=https://forum.flightgear.org/viewtopic.php?p=246659#p246659 |title=FGMEMBERS: The Family |author=IAHM-COL |date=Thu Jun 11, 2015 |publisher=FlightGear forum |accessdate=Fri Jun 12, 2015 }}</ref> Common other licenses are the Creative Commons licenses.
  11.  
  12. {| class="wikitable"
  13. ! Group !! Location !! Content !! Remarks
  14. |-
  15. | FGDATA || https://sourceforge.net/p/fgdata/submodules/ci/next/tree/
  16. | Fork of the FGDATA repository
  17. | Is this a part of FGMEMBERS? Group maintained by IAHM-COL alone (Jun 2015).
  18. |-
  19. | FGMEMBERS || https://github.com/FGMEMBERS
  20. | GPL licensed aircraft
  21. |
  22. |-
  23. | FGMEMBERS-NONGPL || https://github.com/FGMEMBERS-NONGPL
  24. | Non-GPL licensed aircraft.
  25. | Group maintained by IAHM-COL alone (Jun 2015).
  26. |-
  27. | FGMEMBERS-SCENERY || https://github.com/FGMEMBERS-SCENERY
  28. | GPL licensed scenery.
  29. | Group maintained by IAHM-COL alone (Jun 2015).
  30. |-
  31. | FGMEMBERS-SCENERY-NONGPL || https://github.com/FGMEMBERS-SCENERY-NONGPL
  32. | Non-GPL licensed scenery.
  33. | Group maintained by IAHM-COL alone (Jun 2015).
  34. |}
  35.  
  36. == How to use ==
  37. === Preparation ===
  38. (Do this only once)
  39.  
  40. Clone the "submodules" fork of fgdata (1.3 GB):
  41.  
  42. <syntaxhighlight lang="bash">
  43. git clone http://git.code.sf.net/p/fgdata/submodules fgdata
  44. </syntaxhighlight>
  45.  
  46. {{Note|You need to redirect your fligthgear launcher to use the new fgdata directory obtained, as the $FG_ROOT. You will also need to match the version file with the version you are running. FGDATA with submodules is available for FG3.4 or later}}
  47.  
  48. ==Init the submodules==
  49.  
  50. You can initialize only a few desired Aircraft [Really, as many as you want]. The update step will only install/update those submodules initialized. per example
  51.  
  52. <syntaxhighlight lang="bash">
  53. cd fgdata
  54. git submodule init Aircraft/777
  55. git submodule init Aircraft/A320neo
  56. git submodule init Aircraft/A330-200
  57. git submodule init Aircraft/{767,Comet-J,Jumbolino,b1900d} # Initializes a comma separated list of aircraft
  58. git submodule init Aircraft/L* #Initializes any aircraft with a name beginning with Capital L
  59. git submodule init Aircraft/[Aa]* #Initializes any aircraft with a name beginning with A or a
  60. </syntaxhighlight>
  61.  
  62. === Download or update Initialized aircraft ===
  63.  
  64. The command update will now allow you to either 1) Install, or 2) Update already installed aircraft on the fly. This command only fetches submodules already initialized, and thus allowing you to control very finely, which aircraft you are interested in obtaining for testing/flying purposes.
  65.  
  66. <syntaxhighlight lang="bash">
  67. git submodule update
  68. </syntaxhighlight>
  69.  
  70. Alternatively, you can specify which particular submdodule you want to update. Notice that this needs to be initialized previously
  71.  
  72. <syntaxhighlight lang="bash">
  73. git submodule update Aircraft/767
  74. </syntaxhighlight>
  75.  
  76. Everyonce in a while, (some of) the aircraft undergo updates, you can fastly update your installed aircraft, by simply doing
  77.  
  78. <syntaxhighlight lang="bash">
  79. git pull
  80. git submodule update
  81. </syntaxhighlight>
  82.  
  83. === Download/update ALL aircraft ===
  84. {{Note|More than 700 aircraft or about 25 GB!}}
  85.  
  86. (At a speed of ~100kb/s, the entire collection of planes, from 14bis to 787-8 took about 6-7 hours!)
  87.  
  88. To obtain all the Aircraft hosted and developed in FGMEMBERS, simply initialize all the package and update. To initialize all the Aircraft, and thus enabling installing all of them, use init command without a parameter.
  89.  
  90. <syntaxhighlight lang="bash">
  91. cd fgdata
  92. git submodule init
  93. </syntaxhighlight>
  94.  
  95. Then, you can update the Initialized aircraf (which in this case means all)
  96.  
  97. <syntaxhighlight lang="bash">
  98. git submodule update
  99. </syntaxhighlight>
  100.  
  101. Importantly, once you have successfully obtained all the aircraft, fetching the newest code by the developers is very easy, fast, and efficient. You do not need to download the complete aircraft(s) again, since git will only download the newest code/changes, which is very convenient manner to maintain yourself updated
  102.  
  103. <syntaxhighlight lang="bash">
  104. cd fgdata
  105. git pull
  106. git submodule update
  107. </syntaxhighlight>
  108.  
  109. == Deinitialize/Deinstall an Aircraft ==
  110.  
  111. To deinstall any Aircraft, simply deinit the respective submodule. This will clear your disk space as well, but you will still be able to reinitialize at a later time
  112.  
  113. Example, deleting the Antonov-An-12 (if previously initialized/updated)
  114.  
  115. <syntaxhighlight lang="bash">
  116. cd fgdata
  117. git submodule deinit Aircraft/Antonov-An-12
  118. </syntaxhighlight>
  119.  
  120. == Footnotes ==
  121. {{appendix}}
  122.  
  123. == Related content ==
  124. * http://forum.flightgear.org/viewtopic.php?f=28&t=25314&start=45#p234592
  125.  
  126. [[Category:Community]]
  127.  
  128. -->
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement