[pkg-fgfs-crew] flightgear 3.2 packaging

[Rebecca Palmer]

I have had Aircraft Center working on an earlier commit with the 
727-230; I haven't yet tested this one.

> Can I try splitting up the package? Do I understand correctly that your
> fgdata_checkers.py would generate different *source* tarballs? (That'd
> be ideal, as flightgear-data easily is the biggest source package as
> well.)
Currently, the script takes an (unpacked) flightgear-data directory as 
input, and generates another one omitting/downsampling parts as 
requested.  (It currently can't output _only_ an optional package, but 
this would be easy to add.)

If we are going to put flightgear-data through NEW, I suggest we make 
the package layout (sizes approximate):
base 136M (includes c172p+ufo; also includes all the sim-wide scripts, 
making it the most likely piece to need a bug-fix upload, so if you're 
splitting the source package you might want to put it by itself)
models 153M
scenery 102M (this has increased greatly since you decided not to split 
it off; might not be needed if you're going to immediately turn 
Terrasync on, but I haven't tested that)
base textures 176M
extra textures 207M optional
(Sizes assuming 'extra' is region-specific scheme and 'base' global 
scheme; another option would be 'base' downsampled and 'extra' full 
resolution, the generic names allow for either)
AI 211M optional
aircraft 305M optional
The optional parts could be Suggests or Recommends, depending on whether 
we're trying to save Debian bandwidth or just offer an option for users 
on poor connections.

> Also, do either of you get warning messages saying that LiberationSans-*.ttf can't be loaded, and see Courier New (or what looks like it) used as a result for most of the text in flightgear?
Is this in Ubuntu 14.04?  Its version of openscenegraph can't load any 
.ttf (#743169, fixed in jessie & utopic).