Re: Adding 787 to FGAddon

Before we give it another go, I suggest we carry over all the changes to 
the FGAddon 787-8 since I first made the merge to create the active repo 
- looks like there have been six, and it's worth examining them since 
they include things like removing possible license violations.

I can create the PR, then once we confirm everything's good to go and 
merge that we should be ready to proceed with the initial migration. 
Would still be a long way to go of course :) but I think we would have 
the hangar track the stable main branch on GitHub since it seems we now can.

On 8/10/26 9:30 AM, Israel Emmanuel wrote:
>
> That's actually super cool. I'll give it a go with the repository and 
> see how it goes. In the meantime, the 787 repo is all compliant, and 
> should be good to go.
>
> On 8/10/26 01:36, James Turner wrote:
>>
>>
>>> On 10 Aug 2026, at 10:30, Frederic T. <[email protected]> wrote:
>>>
>>> Oh wait I missed that, I don't have to mess with SVN anymore ? :D
>>
>> I didn’t announce it yet, because it’s a beta feature. I’m going to 
>> start with it on trunk and check the ZIPs are sane (and especially 
>> the updating) before we start making any structural changes. But for 
>> a ‘new’ aircraft the risk is lower.
>>
>>> How do we add to the catalog config ?
>>>
>> Make MRs against:
>>
>> https://gitlab.com/flightgear/fgmeta-python/-/tree/next/catalog?ref_type=heads
>>
>> Kind regards,
>> James
>>
>>
>> _______________________________________________
>> Flightgear-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
> _______________________________________________
> Flightgear-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
-- 

*IskenderWang*

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel