Control: forwarded -1 http://hub.qgis.org/issues/13279
On 05/04/2016 10:40 AM, Bas Couwenberg wrote: > There is currently no explicit support for SAGA >= 2.2.4. There is an > outstanding issue in the upstream issue tracker about changes required > for SAGA 2.24: > > http://hub.qgis.org/issues/14735 The upstream issue was just rejected stating: " This known issue with SAGA. SAGA devs break API in every minor version making maintenance really hard. " Further discussion is this issue: http://hub.qgis.org/issues/13279 > With the frequent API breakage in new SAGA releases, and the lack of > manpower in the QGIS project to keep the SAGA processing plugin updated, > I remain sceptical of our ability to support SAGA in QGIS. > > https://lists.osgeo.org/pipermail/qgis-developer/2015-December/040797.html > > I'd like to hear Johans opinion on SAGA support in QGIS. Not updating SAGA to newer upstream releases when we have a working QGIS/SAGA combination is not a very appealing option. It does seem to me the best way to have a working combination in stable without the need for additional repositories (backports or 3rd party). If the SAGA developers were to adopt LTS releases, this would greatly getting those versions supported in QGIS. We can then target those releases for inclusion in stable. In the mean time there is not much we as distribution maintainers can do about this issue, unless we stop keeping SAGA current to allow QGIS to catch up or actively port the SAGA Processing support in QGIS for every new SAGA release. @Johan, what can you tell us about this issue from the SAGA point of view? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 _______________________________________________ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
