On 07/31/2013 05:24 PM, Markus Wanner wrote: > I've pushed upstream/2.10.0 and an update to the debian packaging of it. > It's based It's based on your changes. I hope that's okay. > > Obviously, it's not of much use without an updated simgear package, > which flightgear depends on. I have updates for that ready as well, but > am not sure where to push to. Just as a heads up: all three are now available on collab-maint and are updated to work together to provide FlightGear 2.10: http://anonscm.debian.org/gitweb/?p=collab-maint/simgear.git http://anonscm.debian.org/gitweb/?p=collab-maint/flightgear-data.git http://anonscm.debian.org/gitweb/?p=collab-maint/flightgear.git I'm still working on it, but it's worth pointing out a few design decisions that may be controversial: - I moved the scenery data package back into the base one, as it's too small to matter (< 10 MiB) and didn't disturb terrasync, either. - Split AI data into its own package (ca. 130 MiB) - Consistently renamed fgfs to flightgear (package names) - Renamed simgear to libsimgear, split to match SONAMES I'd still like to: - Use debhelper 7 for simgear as well. And get rid of the static variant of that library in libsimgear-dev. It would simplify rules a lot. Anybody opposed to that? I envision flightgear-data-base to be a package that's sufficient to run flightgear on. No AI, no object models, only the default c172 aircraft. (Of course, that currently emits lots of warnings and load errors. I hope to be able to get rid of those eventually.) Regards Markus Wanner
Attachment:
signature.asc
Description: OpenPGP digital signature