FlightGear Newsletter September 2014: Difference between revisions

Jump to navigation Jump to search
→‎Aircraft are moved to SVN: +- heading; + subheadings; etc
No edit summary
(→‎Aircraft are moved to SVN: +- heading; + subheadings; etc)
Line 5: Line 5:
{{Newsletter-cover-item|FlightGear 3.2 released (this time for real!)}}<br/>
{{Newsletter-cover-item|FlightGear 3.2 released (this time for real!)}}<br/>
{{Newsletter-cover-item|DDS feedback needed}}<br/>
{{Newsletter-cover-item|DDS feedback needed}}<br/>
{{Newsletter-cover-item|Aircraft are moved to SVN}}<br/>
| valign="top" width="33%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|(this is the second column)}}<br/>
{{Newsletter-cover-header|(this is the second column)}}<br/>
Line 29: Line 30:
Continue reading at [[Switching default texture format to DDS]]...
Continue reading at [[Switching default texture format to DDS]]...


== Aircraft are hosted on SVN ==
== Aircraft are moved to SVN ==
 
Some months ago we decided to host our aircraft on an SVN repository in order to relieve the fgdata.
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.
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/
We finally moved all our aircraft to '''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.
This repository is named "FGAddon" because its content is not required to run FlightGear, as a file not required but providing a new feature (in this case it's aircraft) is usually called an "addon".


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.
=== Advantages ===
On the 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 the 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 release is built.


A mini HowTo:
=== A mini HowTo ===
* For Windows: install TortoiseSVN (http://tortoisesvn.net/)  
* For Windows: Install TortoiseSVN (http://tortoisesvn.net/)  
* For Linux/Mac: install SVN
* For Linux/Mac: Install SVN


Then to pick an aircraft (in this example we pick up the DR400-dauphin):
Then to pick an aircraft (in this example we pick up the DR400-dauphin):
Line 56: Line 55:
If you used to use GIT it's finally not so different to run "git clone" or "git pull" ;-)
If you used to use GIT it's finally not so different to run "git clone" or "git pull" ;-)


 
=== Background ===
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
For our aircraft developers who usually don't read the mailing list (I hope they 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 ==

Navigation menu