577
edits
m (Updated section link in header) |
No edit summary |
||
Line 28: | Line 28: | ||
Continue reading at [[Switching default texture format to DDS]]... | Continue reading at [[Switching default texture format to DDS]]... | ||
== Aircraft are hosted on SVN == | |||
Some months ago we decided to host our aircraft on an SVN repository in order to relieve the fgdata. | |||
The fgdata repo would be a mirror of the base package. | |||
We finally moved all our aircraft in '''the new SVN repo''': http://sourceforge.net/p/flightgear/fgaddon/ | |||
This repository is named "FGAddon" because its content is not required to run FlightGear, a file not required but providing a new feature (in this case it's aircraft) is usually called an "addon". | |||
On user-side, the most important feature is to be able to checkout only wanted aircraft, you do no longer need to download the +400 aircraft at once. | |||
On developper-side, the most important interest is to have a base-package like which is lighter to sync for new contributors and easier to maintain when realease is built. | |||
A mini HowTo: | |||
* For Windows: install TortoiseSVN (http://tortoisesvn.net/) | |||
* For Linux/Mac: install SVN | |||
Then to pick an aircraft (in this example we pick up the DR400-dauphin): | |||
svn co https://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/DR400-dauphin | |||
Then you can regularly pick the last update with | |||
svn up | |||
If you used to use GIT it's finally not so different to run "git clone" or "git pull" ;-) | |||
PS: for our aircraft developer who usually don't read the mailing list (I hope it doesn't exist but just in case), please read this topic: https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/DUB127-W168600DE27B42094E5263EC3C10%40phx.gbl/#msg32809711 | |||
== Interview with a contributor == | == Interview with a contributor == |
edits