Re: [Qgis-developer] (Yet again) SAGA support badly broken in QGIS
My opinion about this (and getting stronger each time, since the
situation is getting worse...) is that we have only two solutions:
1) fork SAGA and have QGIS depend on that forked software, which we
will (in principle) not upgrade.
2) embed a fixed version of SAGA, and use only that one. SAGA should
be treated like a library: we support a given version, and not all
version of it. If you want to use a different one, you cant (just like
QGIS uses Python2 and a user cannot use Python3)
I will be happy to discuss about this.
2016-05-31 20:01 GMT+02:00 Paolo Cavallini <firstname.lastname@example.org>:
> Hi all,
> SAGA dev team have changed (2.2.7) once more a crucial parameter , so
> raster commands (probably all) are broken in QGIS/Processing.
> IMHO it is infeasible to chase breaking changes in point releases, so I
> suggest either saga devs stop breaking compatibility, except for major
> releases, or Debian stop upgrading the package not to break qgis support.
> Opinions most welcome.
> All the best.
> 2016-05-31T17:54:27 0 SAGA execution commands
> io_gdal 0 -TRANSFORM 1 -INTERPOL 0 -GRIDS
> Risultato della console di esecuzione di SAGA
> Unknown option 'INTERPOL'
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> Qgis-developer mailing list
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer