FlightGear hangars: Difference between revisions

Jump to navigation Jump to search
Removal of the ==Creating a hangar== section, as this is now in Hangar catalog.
No edit summary
(Removal of the ==Creating a hangar== section, as this is now in Hangar catalog.)
Line 36: Line 36:
   |added  =  May 10th, 2016  
   |added  =  May 10th, 2016  
   |script_version = 0.39  
   |script_version = 0.39  
  }}</ref>
== Creating a hangar ==
it would be great to start seeing some of the other aircraft hangar developers distributing their work this way. From an end user perspective, you just add a single url to a single catalog file, and then you have instant access to download and update all the aircraft in that catalog. James has done some really cool gui work to help make aircraft easy to find and install for end users.<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35488445/
  |title  =  <nowiki> Re: [Flightgear-devel] Testing changes to update_catalog.py </nowiki>
  |author =  <nowiki> Curtis Olson </nowiki>
  |date  =  Nov 13th, 2016
  |added  =  Nov 13th, 2016
  |script_version = 0.40
  }}</ref>
the update catalog script is in flightgear-fgmeta/catalog/ and called update-catalog.py<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35488445/
  |title  =  <nowiki> Re: [Flightgear-devel] Testing changes to update_catalog.py </nowiki>
  |author =  <nowiki> Curtis Olson </nowiki>
  |date  =  Nov 13th, 2016
  |added  =  Nov 13th, 2016
  |script_version = 0.40
  }}</ref>
Next to the update-catalog.py script is a directory called fgaddon-catalog/ To run the script, just execute: "./update-catalog.py fgaddon-catalog" The idea is to create a subdirectory tree for each catalog you wish to maintain. This subdirectory can be called anything you like and it contains the config and administrative files for maintaining the catalog. I recommend you take a quick look through the script to make sure there aren't any hard coded paths that I missed. And of course the config file inside the catalog directory will need to be adjusted for each new hangar. The script doesn't automatically upload the aircraft like your original did, instead it just builds the content locally and I sync with a separate (rsync-based) script. I maintain a local copy of the flightgear ftp tree and have a script that rsyncs the whole tree at once.<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35488445/
  |title  =  <nowiki> Re: [Flightgear-devel] Testing changes to update_catalog.py </nowiki>
  |author =  <nowiki> Curtis Olson </nowiki>
  |date  =  Nov 13th, 2016
  |added  =  Nov 13th, 2016
  |script_version = 0.40
   }}</ref>
   }}</ref>


Navigation menu