Re: The endless influx of low-quality, low-realism, quantity-over-quality aircraft into FGAddon
Florent Rougon via Flightgear-devel <[email protected]>
| Newsgroups | gmane.games.flightgear.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, Le 25/05/2026, [email protected] a écrit: > i'm aware there's a script to process craft directories located somewhere to > create the catalog file but i don't know where the script is and do not see > anything in the UI pointing me in that direction or to full detailed > instructions on how to use it... especially if the catalog is to contain craft > from various repos across the 'net... fg-build-catalog is presented here in its repo (scroll down for the rendering of its README.md): https://gitlab.com/flightgear/fgmeta-python/-/tree/next/catalog?ref_type=heads If you have a single dir containing aircraft (say, a particular FGAddon branch or the trunk) and you want to create a hangar containing a subset of these aircraft, then <include> should help (its reverse is <skip>; not sure both can be used at the same time). An example I used for testing (this belongs to catalog.config.xml file): <scm> <type>no-scm</type> <update type="bool">false</update> <path>flo-test-catalog/repo</path> <include>bluebird</include> </scm> In this case, I had a directory containing a few craft zip files, and for some tests I wanted to only process the 'bluebird'. If you look at the official catalog files, e.g. https://gitlab.com/flightgear/fgmeta-python/-/blob/next/catalog/stable-2024-catalog/catalog.config.xml?ref_type=heads you'll see elements like this: <scm> <type>svn</type> <path>svn-2024.1</path> <repo>svn://svn.code.sf.net/p/flightgear/fgaddon/branches/release-2024.1/Aircraft</repo> <!-- skip the following aircraft dirs --> <skip>NTPS</skip> <skip>c172</skip> <skip>tu134</skip> </scm> (and one with <include-only>yes</include-only> for includes relying on files from FGData) Git is also supported. I'm not the author of fg-build-catalog, so I know it rather superficially, however I believe it makes it possible to compile aircraft from different source repositories by means of several <scm> elements. Of course you'd also need to make the result available to your users, therefore upload it somewhere unless you only use the hangar locally. fg-build-catalog's catalog.config.xml files may contain <upload> elements that support rsync over SSH (cf. the official files, again). Regards -- Florent _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel