Base Package Assembly

This article has been nominated for deletion since 9 January 2026. To discuss it, please visit the talk page. Do not remove this tag until the discussion is closed. Reason for the nomination: Outdated now that aircraft have been split from FGData years ago

Objective

To move forward with restructuring the FGData repository, some discussion is needed on how different groups of people use the system. — James Turner (2015-02-25). [Flightgear-devel] FGData splitting / assembling the base package. (powered by Instant-Cquotes)

Would it be perhaps beneficial if the people engaged in this discussion created a wiki page with structured checklist of all known problems and issues? Then those suggesting a different solution could check and state how their solution would solve (or ignore) those issues. It would make it easier (I hope) to concentrate on the relative merits of various proposals. — Edheldil (2015-02-27). Re: [Flightgear-devel] FGData splitting / assembling the base package. (powered by Instant-Cquotes)

Status

I am going to commence reducing FGDATA this weekend. The reasons for that action have been discussed here and on the forum in epic detail, so I won't repeat them. The result will be a new and much smaller git repository and it will only have the c172p and the ufo remaining. To avoid any unnecessary extra work, I will temporarily remove all contributors with write access except 2 or three admins on Friday afternoon (Central European Time Zone). — Torsten Dreyer (2015-03-05). [Flightgear-devel] FGData size reduction. (powered by Instant-Cquotes)

Next, I'll do a initial commit of the base package aircraft to fgaddon/svn. Following that, I create a new git repo for a smaller git fgdata and push it to sourceforge. Finally, we re-add contributors with push permission. If anything goes wrong, the original fgdata will remain intact and can serve as a fallback. — Torsten Dreyer (2015-03-05). [Flightgear-devel] FGData size reduction. (powered by Instant-Cquotes)