On 03/21/2014 03:43 PM, Francesco P. Lovergine wrote:
> The point is: is it possible to build without libv8-dev on those
> archs and still having a working product? In that case we could
> change the b-d chain appropriately.
Yes, we drop or loosen the b-d on libv8-dev and still have a useable
package for osgEarth.
On 03/21/2014 03:37 PM, Julien Cristau wrote:
> What's the reason to make it mandatory? As far as I can tell from the
> diff between 2.4 and 2.5 it's still optional upstream...
In the spirit of enabling most functionality of osgEarth I chose to
build depend on libv8-dev.
It has the welcome side benefit of limiting the number of architectures
on which the full QGIS dependency chain is supported.
When we don't require libv8-dev for osgEarth, I expect it to FTBFS on
some of the ports, and the same goes for whose osgearth-dev build
dependency is satisfied when osgearth is fixed on the ports.
The topic of limiting the architectures for QGIS were discussed in the
osgEarth 2.5 thread on debian-gis@ last month, see:
While I'd like to support the ports as much as possible, it's very time
consuming, not only because I need to request guest-accounts from DSA first.
The security status of libv8 is also a bit worrisome, and another reason
to drop the build dependency. We just need to deal with a number of
FTBFSes for osgEarth and QGIS then.
GPG Key ID: 4096R/E88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Pkg-grass-devel mailing list