4,400
edits
Simplifying Aircraft Deployment: Difference between revisions
Jump to navigation
Jump to search
m
Bot: Automated text replacement (-aircrafts +aircraft)
m (→Updating) |
m (Bot: Automated text replacement (-aircrafts +aircraft)) |
||
| Line 71: | Line 71: | ||
== Deletion/Uninstallation == | == Deletion/Uninstallation == | ||
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 | 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): to avoid possibly corrupting system-level FG_ROOT | * aircraft folders would reside in a user-specific location (i.e. $FG_HOME/Aircraft): to avoid possibly corrupting system-level FG_ROOT | ||