128
edits
Simplifying Aircraft Deployment: Difference between revisions
Jump to navigation
Jump to search
→Possible Steps
mNo edit summary |
|||
| Line 26: | Line 26: | ||
= Possible Steps = | = Possible Steps = | ||
There are three actions that can be carried out on aircraft:- | |||
# Install | |||
# Update | |||
# Delete (Uninstall) | |||
Installation involved checking if the aircraft exists (better to pull the list of available aircraft to allow user selection). We should check for version compatibility of the install FlightGear binary. If a aircraft is not compatible with the current version of FlightGear, do not allow the installation of it. | |||
Updating an aircraft invloves checks if the aircraft is installed and then comparing the installed version with the latest version on a server. if the versions are the same, alert the user that the versions are the same and no update will occur. | |||
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 should check to ensure that there are no dependencies for the aircraft. An example of which is an aircraft that makes use of another aircrafts instruments and is not centrally installed. | |||
== Extracting a new aircraft == | == Extracting a new aircraft == | ||
| Line 39: | Line 50: | ||
# Optionally report back to the launcher that the sub process is done. | # Optionally report back to the launcher that the sub process is done. | ||
# Sub process exits. | # Sub process exits. | ||
= Related Mailing List Discussions = | = Related Mailing List Discussions = | ||