20,741
edits
Catalog metadata: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
No edit summary |
mNo edit summary |
||
| Line 11: | Line 11: | ||
}} | }} | ||
}} | }} | ||
{{FGCquote | |||
| The goal is that no one except people working on an individual aircraft should care where it’s developed at all (on GitHub, in a private SVN repo, stored as sheets of paper in a filing cabinet). SCM systems are not distribution/release systems, we’ve simply been using them in that fashion by accident. | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33550567/ | |||
|title=<nowiki>Re: [Flightgear-devel] FGData size reduction</nowiki> | |||
|author=<nowiki>James Turner</nowiki> | |||
|date=<nowiki>2015-03-06</nowiki> | |||
}} | |||
}} | |||
{{FGCquote | |||
|If you wish to dig into the package system, and create some tooling so it’s easy to publish releases from a Git repo to a web-host, please do. The current script is in fgmeta; see ‘create_catalog.py’ which runs over FGData of course, but you can imagine something similar for any SCM store containing several aircraft. There’s additional features that can be added of course, such as support for ‘beta’ or ‘testing’ versions of aircraft, being able to exist alongside stable versions. That would require some C++ hacking on the client side but pretty straightforward stuff I think. | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33550567/ | |||
|title=<nowiki>Re: [Flightgear-devel] FGData size reduction</nowiki> | |||
|author=<nowiki>James Turner</nowiki> | |||
|date=<nowiki>2015-03-06</nowiki> | |||
}} | |||
}} | |||
== Supported Tags == | == Supported Tags == | ||
{{Note|Please do not extend this list without discussion and agreement.}} | {{Note|Please do not extend this list without discussion and agreement.}} | ||