FlightGear CVS: Difference between revisions
No edit summary |
|||
| Line 9: | Line 9: | ||
* [[Using TortoiseCVS with FlightGear]] | * [[Using TortoiseCVS with FlightGear]] | ||
* [[Keeping FlightGear (win32) up to date without compiling]] | * [[Keeping FlightGear (win32) up to date without compiling]] | ||
Linux (Ubuntu/Debian): Very easy | |||
* Just use the download_and_compile.sh script, instructions here:[[Scripted_Compilation_on_Linux_Debian/Ubuntu]] | |||
Mac: Slightly trickier: | Mac: Slightly trickier: | ||
Revision as of 21:28, 12 July 2009
In the field of software development, the Concurrent Versions System (CVS), also known as the Concurrent Versioning System, provides a version control system based on open-source code. Version control system software keeps track of all work and all changes in a set of files, and allows several developers (potentially widely separated in space and/or time) to collaborate. This means that the newest stuff, which are still in development, are available in CVS before they do in the stable release. CVS has become popular in the open source software world and is released under the GNU General Public License.
FlightGear and CVS
FlightGear's CVS is available here and can be considered as the most up-to-date version of the flightsimulators source and aircraft. To run CVS aircraft the user need to use the CVS, to prevent bugs and faults. The CVS Changelog shows all updates made to the CVS repository.
How to use FlightGear's CVS
Windows: Easy! The following instructions will lead you to your goal. They are very similar, you will probably not have to read all of them:
- Flightgear 1.0 to CVS : Piece of Cake
- Using TortoiseCVS with FlightGear
- Keeping FlightGear (win32) up to date without compiling
Linux (Ubuntu/Debian): Very easy
- Just use the download_and_compile.sh script, instructions here:Scripted_Compilation_on_Linux_Debian/Ubuntu
Mac: Slightly trickier:
If you want to get really into it, see also:
| |||||||||||