Package: src:oolite Followup-For: Bug #863788 Hello.
Upstream relies on a very old copy of the Mozilla javascript interpreter (libmozjs/spidermonkey), downloaded during the build from a private URL, without electronic signature. This hack protects most users from the (frequent) API changes, but does not fit Debian maintenance standards. So I have migrated the package to libmozjs-dev, then libmozjs185-dev. libmozs-24-dev, or the more recent firefox-dev (= 52) use many C++ features. The .h files are incompatible with C, thus with Objective-C. I am reluctant to invest the huge required efforts, while the only sensible solution seems to me that upstream switch to a library giving a bit of consideration to API consistence and stability. A quick search gives two candidates, libjavascriptcoregtk and plasma-scriptengine-javascript, both probably available in all major systems like GTK and KDE. I will probably have to remove Oolite from Debian after the freeze. @Chris: I am CCing you because as far as I know you are the upstream contact for Oolite on Linux systems. If you bring the discussion to some Oolite public place, please inform me so that I can add a link to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863788.
