Simplifying Aircraft Deployment: Difference between revisions

Simplifying Aircraft Deployment (view source)

92 bytes added , 25 October 2009

m

→‎Desirable Long-Term Goals: adding request from sourceforge tracker

2,561

edits

@@ Line 23: / Line 23: @@
 * allow aircraft to be relocated/moved (renamed) within base package
 * allow aircraft to be used without requiring an installation
-* allow aircraft to be installed in and used from custom directories (i.e. non-base package, as in ~/.fgfs/Aircraft or support something like --user-aircraft=/folder/with/non-base-package-aircraft) [http://www.flightgear.org/forums/viewtopic.php?t=79] [http://mail.flightgear.org/pipermail/flightgear-devel/2004-November/032282.html]
+* allow aircraft to be installed in and used from custom directories (i.e. non-base package, as in ~/.fgfs/Aircraft or support something like --user-aircraft=/folder/with/non-base-package-aircraft) [http://www.flightgear.org/forums/viewtopic.php?t=79] [http://mail.flightgear.org/pipermail/flightgear-devel/2004-November/032282.html] [http://sourceforge.net/tracker/index.php?func=detail&aid=1905704&group_id=583&atid=350583]
 * allow aircraft to be run from tarballs/archives to allow users to test aircraft easily (Libraries to transparently access archives likes directories: [http://zziplib.sourceforge.net/ ZZIPLIB] [http://icculus.org/physfs/])
 * provide support for proper dependency tracking between aircraft and common resources [http://www.flightgear.org/forums/viewtopic.php?t=1135]