[pkg-fgfs-crew] Bug#714260: Helping with flightgear package

[Markus Wanner]

On 08/11/2013 05:31 PM, Scott Howard wrote:
> I'll be happy to upload, just let me know when everything is ready
> (flightgear, simgear, libraries, etc.)
> I cannot test the package myself, my hardware isn't good enough - but
> I can make sure it is debian policy compliant and rely on your own
> testing.

I just read that the 2.12 release got postponed to September. So I
currently think it still makes sense to upload 2.10 and gain experience
with it. It's certainly quite a step since 2.6.

Scott, I now consider the packaging here ready for upload to unstable.
Please review:

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

Note that flightgear-data is special in that the origin files are not
included in the git tree. Please get the base data from one of the
mirrors and symlink to fgfs-base_2.10.0.orig.tar.bz2 (723 MiB). Two
possible mirrors are:

> ftp://ftp.de.flightgear.org/pub/fgfs/Shared/FlightGear-data-2.10.0.tar.bz2
> ftp://ftp.kingmont.com/flightsims/flightgear/Shared/FlightGear-data-2.10.0.tar.bz2


I'm a DM and would also appreciate upload permissions. Shall I add
myself as an uploader on these packages?


Some implementation notes: I changes the simgear library to use
debhelper 7 as well. This strips the static variant, which I think is
not needed.

I didn't touch how the data package is split, yet. Since my last mail,
that is. I.e. compared to 2.6, I merged scenery back into the base
package, but split out AI, which is a lot bigger.

However, according to upstream, it's not save to leave away portions of
the provided data package (certainly not simple portions like entire AI,
Models, Scenery or Aircraft directories). Thus, strictly speaking, all
data packages are required. And given former bugs, I now simply made all
data packages a dependency. That's a bit unfortunate, but safe.

I intend to look into splitting data packages or providing some kind of
download manager. Together with a better integration with terrasync. But
I don't want to withhold the current packaging because of that.

Regards

Markus Wanner