[pkg-fgfs-crew] Backporting 3.4.0 to wheezy / Tightening flightgear's Build-Depends

[Florent Rougon]

Hi,

Markus Wanner <markus at bluegap.ch> wrote:

> On 02/20/2015 10:46 AM, Florent Rougon wrote:
>> Good, thank you. I built simgear, flightgear and flightgear-data 3.4.0 on
>> unstable from the Git repo on alioth and tested a few hours. It all
>> seems to work fine, including the web gui. :-)
>
> Very cool! Thanks for testing (TBH I didn't quite have as much time for
> tests).

You're welcome. Also, backporting flightgear 3.4.0 to wheezy showed that
its Build-Depends could be tightened a bit more:

  - sqlite 3.7.14 or later is required because of sqlite3_close_v2()
    (cf. <http://www.sqlite.org/changes.html>);

  - the version of hts_engine in wheezy is too old (does not seem to
    have HTS_Engine_set_speed()); I don't know the exact minimum version
    required, but of course version 1.08 present in sid is OK
    (/usr/share/doc/libhtsengine-dev/changelog.gz is very terse).

I built flightgear with the following patch:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: flightgear.BD.diff
Type: text/x-diff
Size: 680 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-fgfs-crew/attachments/20150222/56a13d26/attachment.diff>
-------------- next part --------------

I can send it in 'git format-patch' format if you wish.

No problem to build simgear and use the flightgear-data/experimental
binary packages as is. flightgear-data-base depends on libjs-jquery-flot
and libjs-leaflet which are not in wheezy. I backported them by means of
a rebuild (which was not fun because of many B-Deps). However, being
arch: all, the packages from sid could probably be used as is.

Regards

-- 
Florent