On Tue, May 31, 2016 at 9:02 PM, Tim Sutton <[email protected]> wrote:
> Hi > > > On 31 May 2016, at 20:44, Victor Olaya <[email protected]> wrote: > > 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. > > > Yes I chatted with Victor about this at the HF and if we want processing > to become something everyone can depend on to work reliably in their > workflows then his way seems like a very good approach. Same approach for > SAGA etc. > > Regards > > > As said in the previous post, I'm willing to maintain one LTR branch in saga, which we could switch eg for every qgis ltr release. https://sourceforge.net/p/saga-gis/mailman/message/35127843/ Kind Regards, Johan
