Re: Adding 787 to FGAddon
James Turner <[email protected]>
| Newsgroups | gmane.games.flightgear.devel |
|---|---|
| Message-ID | <[email protected]> |
> On 6 Aug 2026, at 19:29, Israel Emmanuel <[email protected]> wrote: > > Hello there! I have access to a much better 787 by IskenderWang on Github, and I'm wondering what the process would be of getting that onto FGAddon. Anyone know how I can do that? Thanks! Sorry for the delayed reply. The traditional method: move the 787 currently in FGaddon to attic (using svn move, I think) Periodically, import some stable state of the new 787 into the relevant FGaddon branches (trunk / stable-2024). However, as of last week, we have an alternative: - add the Git repo (and correct branches) to the catalog config, and the build scripts will grab the 787 directly from GitHub. And then we move the 787 in SVN to attic as before. All of this depends on the upstream (GitHub) 787 being license-compatible of course, and the other ‘legal’ stuff : what I wrote here is just about the mechanics of it. But for sure, many people want a good 787, and the one in FGaddon is incomplete and not maintained. Kind regards, James _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel