Re: c172p in fgdata

Not a concern for me.

regarding the packaging scripts... I think you are saying the release 
packages will still contain the C172p, but using a different method. 
Does this require a configuration change to how the Launcher is 
shipped?  Trying to understand how a new user will still get the UFO and 
C172p out-of-box.

Scott

On 6/23/2026 3:52 AM, Stuart Buchanan wrote:
> Hi Folks,
>
> As you will know, we currently have two aircraft in the fgdata git 
> repo - the ufo and c172p. The c172p is synced manually by me on an 
> irregular basis from the c172p-team repo.  Thanks to the c172p-team 
> for their work maintaining and improving the aircraft.
>
> Our packaging scripts are capable of packaging up the c172p directly 
> from the c172p-team repo instead, so we could just remove the c172p 
> from fgdata.  Doing so would remove the dependency on someone doing a 
> manual sync,  keep the packaged c172p more up to date, and reduce the 
> size of fgdata.
>
> The downside to this approach is that folks using git fgdata would 
> no-longer have a real aircraft available for testing within fgdata 
> itself.
>
> Is that an issue for any developers?
>
> Personally, I have external aircraft checkouts already, and spend most 
> of my time "flying" the ufo!
>
> Best regards,
>
> -Stuart
>
>
> _______________________________________________
> 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