Simplifying Aircraft Deployment: Difference between revisions

Jump to navigation Jump to search
reorganisaed the page slightly.
(Expanded Current Limitations section)
(reorganisaed the page slightly.)
Line 1: Line 1:
{{stub}}
{{stub}}


== Intro ==
= Intro =
This page is dedicated to collecting and discussing possible steps to help FlightGear aircraft become more easily deployable. In particular, shortcomings of the current approach of deplyoing aircraft are meant to be identified and addressed.
This page is dedicated to collecting and discussing possible steps to help FlightGear aircraft become more easily deployable. In particular, shortcomings of the current approach of deplyoing aircraft are meant to be identified and addressed.


=== Related Mailing List Discussions ===
= Related Mailing List Discussions =
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg14052.html
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg14052.html


== 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
Line 13: Line 13:
* 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
* 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 ===
 
= Desirable Long-Term Goals =
 
 
* allow aircraft to be fully searchable based on aircraft-type/development status
* allow aircraft to be downloaded from within FlightGear
* allow aircraft to be installed  from within FlightGear
* allow aircraft to be uninstalled/removed from within FlightGear
* allow aircraft to be updated from within FlightGear
* allow aircraft to be copied/duplicated within base package
* allow aircraft to be relocated/moved (renamed) within base package
 
= Possible Steps =
 
== 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.
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.


Line 26: Line 40:
# Sub process exits.
# Sub process exits.


== Desirable Long-Term Goals ==
* allow aircraft to be fully searchable based on aircraft-type/development status
* allow aircraft to be downloaded from within FlightGear
* allow aircraft to be installed  from within FlightGear
* allow aircraft to be uninstalled/removed from within FlightGear
* allow aircraft to be updated from within FlightGear
* allow aircraft to be copied/duplicated within base package
* allow aircraft to be relocated/moved (renamed) within base package


== Possible Steps ==


== Related Mailing List Discussions ==
== Related Mailing List Discussions ==
128

edits

Navigation menu