128
edits
Simplifying Aircraft Deployment: Difference between revisions
Jump to navigation
Jump to search
Expanded Current Limitations section
mNo edit summary |
(Expanded Current Limitations section) |
||
| Line 8: | Line 8: | ||
== Current Limitations == | == Current Limitations == | ||
* 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 need to be manually installed by extracting archive to base package | * aircraft need to be manually installed by extracting archive to base package | ||
* Most distributions of Linux will install the FG Root as read only to standard users.<br>This means that the user is unable to extract a new aircraft to the same directory tree. See subsection | |||
=== Extracting a new aircraft === | |||
As mentioned above, installing to the distribution approved location such as /usr/local/share/FlightGear/ (for Ubuntu/Debian like distros) would require using something like sudo and prompting for the users password. However, this could be done in helper programs such as fg_run. Despite implementing this it still may not be successful as most distributions do not allow general users to use sudo. | |||
One way around this is to allow the setting of a second location to store aircraft. | |||
Process | |||
# User selects an aircraft which is not available | |||
# Sub process is created to deal with the request (rather than holding up the entire launcher) | |||
# Process will commence downloading the selected aircraft | |||
# Extract the aircraft to a user writable Aircraft directory. | |||
# Optionally report back to the launcher that the sub process is done. | |||
# Sub process exits. | |||
== Desirable Long-Term Goals == | == Desirable Long-Term Goals == | ||