4,400
edits
Simplifying Aircraft Deployment: Difference between revisions
Jump to navigation
Jump to search
m
Link to special directory articles
No edit summary |
m (Link to special directory articles) |
||
| Line 12: | Line 12: | ||
* aircraft need to be manually downloaded from FlightGear webpage. | * aircraft need to be manually downloaded from FlightGear webpage. | ||
* aircraft need to be manually checked for version compatibility | * aircraft need to be manually checked for version compatibility | ||
* aircraft authors need to provide separate *-set.xml files for their aircraft to account for different versions of FlightGear (i.e. see $FG_ROOT/Aircraft/bluebird) | * aircraft authors need to provide separate *-set.xml files for their aircraft to account for different versions of FlightGear (i.e. see [[$FG_ROOT]]/Aircraft/bluebird) | ||
* aircraft dependencies need to be determined and satisfied manually | * aircraft dependencies need to be determined and satisfied manually | ||
* aircraft need to be manually installed by extracting archive to base package | * aircraft need to be manually installed by extracting archive to base package | ||
| Line 78: | Line 78: | ||
Deleting an aircraft is even easier as we may not need to talk to the server. Instead we check if the aircraft is installed (and unmodified) and should check to ensure that there are no dependencies for the aircraft. An example of which is an aircraft that makes use of another aircraft's instruments and is not centrally installed. Preferably, aircraft would by default only be deleted/uninstalled if they match the following requirements: | Deleting an aircraft is even easier as we may not need to talk to the server. Instead we check if the aircraft is installed (and unmodified) and should check to ensure that there are no dependencies for the aircraft. An example of which is an aircraft that makes use of another aircraft's instruments and is not centrally installed. Preferably, aircraft would by default only be deleted/uninstalled if they match the following requirements: | ||
* aircraft folders would reside in a user-specific location (i.e. $FG_HOME | * aircraft folders would reside in a user-specific location (i.e. [[$FG_HOME]]Aircraft): to avoid possibly corrupting system-level FG_ROOT | ||
* aircraft folder must be in pristine state/untouched: | * aircraft folder must be in pristine state/untouched: | ||
** no removed files | ** no removed files | ||