AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Flightgear download aircraft11/10/2023 ![]() ![]() Other parts of the FlightGear infrastructure were already hosted by SourceForge, making the move a natural one. This catalysed the split of fgdata-old and a switch to the SourceForge open source infrastructure for the hosting of the VC repositories. In late 2014, Gitorious, the provider of the open source infrastructure for the FlightGear source code and data repositories announced that it would shut its services down by May 2015 due to its acquisition by GitLab. This would facilitate community management and maintenance of the aircraft while at the same time providing modularity and smaller downloads and smaller local repository sizes. After half a decade of planning, it was decided that the best solution for FlightGear aircraft development would be a single centralized Subversion repository. In the planning stages, the repositories were known as fgdata-old splitting into FGData (a.k.a. From this date until the end of 2014, the design of the fgdata split was discussed on the development mailing list and summarised in the FlightGear Git: splitting fgdata wiki article. However this attempt failed and was abandoned. Each aircraft was placed in its own Git repository and all aircraft linked back to fgdata using a Git submodule approach. A first splitting attempt was organised by Gijs de Rooy and announced on Octo. With time as the project grew, the size and scope of the fgdata repository mushroomed, mainly due to the growing number of aircraft stored in $FG_ROOT/Aircraft, so that a split was inevitable. Due to bandwidth issues, it was decided that the new repositories would be hosted on the Gitorious open source infrastructure. These events resulted in a mass migration of all the CVS repositories to Git repositories. In May 2010, development was interrupted by the infamous "coffee incident" which resulted in the loss of Curtis' home server hosting all of the FlightGear repositories. To allow for the legal redistribution of these assets as part of the FlightGear distribution, a GPLv2 only policy was adopted. Therefore it was decided that much of this FlightGear content would be assembled and stored together in a new centralised CVS repository called fgdata, which was created on October 22, 2000. These assets were not organised and were scattered across different parts of the internet. The first commits were to the original flightgear and simgear CVS version control repositories.Īs the project grew, so did the size, quantity, and quality of the FlightGear assets. Therefore starting on May 16, 1997, Curtis Olson relaunched development with a new project based on the OpenGL libraries, allowing a functional flight simulator to be put together in a short period of time. However this was a huge task that came to an unfinished halt at the start of 1997 as the main developer, Eric Korpela, was finishing his thesis. Part of the initial goals were to develop 2D and 3D graphics routines for the simulator. The FlightGear project was conceived on Apby David Murr who proposed a new flight simulator to be developed by volunteers. 7.4 Connecting an existing git repository to FGAddon.7.3 Sending external git repository changes into FGAddon.5.2 Commit blocking by pre-commit hooks.4.3.3 Copying files within one aircraft.3.1 Contact the original aircraft authors.Also, if using the lastest nightly releases or a self-compiled version of FlightGear from FlightGear's Git version control repositories, using FGAddon allows the aircraft to be updated to the latest development versions. However, as stable releases from FlightGear version 3.4 onwards are tagged and present within the FGAddon repository, the Subversion tools can be a convenient way to obtain individual aircraft or the entire official hangar of approximately 500 aircraft. When using a stable FlightGear release, it is best to obtain aircraft with a matching version number from the FlightGear download pages. ![]() The FGAddon aircraft development repository should be considered unstable. These are aircraft that are not part of the base package (the aircraft that are included in the base package - the Cessna 172P and the UFO - are kept in the FGData repository), but are tagged with each stable release for the FlightGear download pages. FGAddon is an Apache Subversion version control repository. The official FGAddon aircraft hangar is a version control repository, hosted on FlightGear's SourceForge infrastructure, and used for the day-to-day development of FlightGear aircraft. ![]()
0 Comments
Read More
Leave a Reply. |