Re: Issues updating planes located in FGAddon

> On 2 Jun 2026, at 19:20, Frederic T. <[email protected]> wrote:
> 
> If we need to do that, we did something wrong, and we are doing it wrong since the beginning - instruments / APs / etc. should not be copied into every aircraft but at the very least be in a separate repository integrated into the aircraft as a git submodule, or even better we have a framework that allows integration of instruments etc. from a repository like FGAddon.

You’re misunderstanding the use case - and exactly the value we get from the current setup. When checking ‘how is the turn indicator using property X’, we can currently do a grep over all of FGaddon, and *see* how many aircraft use it, and which use particular properties in their animations, etc, etc.

Without some tooling to replace that, we’d make it much harder to do incremental changes to anything used by lots of aircraft: the ‘see what everything in FGaddon is doing’ is the best (only?) way we have to gauge how the API core-FG exposes (properties  + Nasal + animations + ….) is used in practice.

Kind regards,
James

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