6,566
edits
FGAddon: Difference between revisions
Jump to navigation
Jump to search
→Obtaining aircraft: The SVN acronym is now explained.
(→Fixing the problem: Cross-link to the #Subversion_properties section.) |
(→Obtaining aircraft: The SVN acronym is now explained.) |
||
| Line 23: | Line 23: | ||
{{caution|If the FlightGear and FGAddon aircraft versions do not match, strange bugs should be expected and the version-mismatch combination will not be supported by the FlightGear community.}} | {{caution|If the FlightGear and FGAddon aircraft versions do not match, strange bugs should be expected and the version-mismatch combination will not be supported by the FlightGear community.}} | ||
With access to the SVN tools, the FGAddon version control repository can be a convenient way for obtaining aircraft for using within a specific FlightGear version directly from the official source. When using the [[FlightGear Build Server|nightly builds]] or a [[Building FlightGear|version controlled copy of FlightGear]], the most up to date in-development versions of the aircraft should be used so the versions match. The following describes how to use the official repository to obtain aircraft from the perspective of a FlightGear user. | With access to the Subversion (SVN) tools, the FGAddon version control repository can be a convenient way for obtaining aircraft for using within a specific FlightGear version directly from the official source. When using the [[FlightGear Build Server|nightly builds]] or a [[Building FlightGear|version controlled copy of FlightGear]], the most up to date in-development versions of the aircraft should be used so the versions match. The following describes how to use the official repository to obtain aircraft from the perspective of a FlightGear user. | ||
=== Preparation === | === Preparation === | ||