[QGIS-Developer] Fwd: GRASS in QGIS

[Rainer Hurling]

Hi Jürgen,

Am 12.10.26 um 16:39 schrieb Jürgen E. Fischer via QGIS-Developer:
> Hi,
> 
> On Mon, 12. Oct 2026 at 09:43:11 +1000, Nyall Dawson via QGIS-Developer wrote:
>> This isn't so straightforward -- it's not like the SAGA or OTB situations,
>> where a user can easily download those as separate installers and then
>> activate a QGIS plugin.
> 
> The GRASS plugin is an optional package in OSGeo4W and Debian.  So QGIS can be
> installed without GRASS - although it was built against it.
> 
> Splitting the GRASS package into tools+libraries and the UI would be another
> option - as we don't use GRASS' GUI.  But I don't know know where the line
> between the two exactly is - splitting off everything that's python might do
> the trick.
> 
> The MSI still included SAGA although QGIS integration is gone (and I'm not sure
> whether the nextgen plugin was revived at all).

I’ve been meaning to update you on the SAGA nextgen plugin and its 
continued support in SAGA for some time now. I’d like to go into more 
detail in a separate email to qgis-dev (thread “SAGA GIS plugin 
maintenance” from May 21); here’s just a bit of preliminary information.

Based on the last official “SAGA processing nextgen” plugin—which is no 
longer functional—the small group of SAGA developers has included a 
version in SAGA starting with version 9.13.0 (from commit a5edc55ce46f) 
that has been adapted for QGIS 4 and generally improved. SAGA can use 
its own tool, the “QGIS Tool Interface Generator,” to install the entire 
plugin provided by SAGA into the QGIS user’s plugin directory. As a 
result, the tool’s descriptions match the installed SAGA version exactly.

More on this and on potential issues with future QGIS 4.4 versions will 
be provided in a separate email. However, that may take a few more days.

Regards,
Rainer Hurling


> Both GRASS GUI and SAGA depend on wxwidgets.
> 
> For the MSI we've split off the transformation grids and now have installers
> for the LTR and LR each with and without grids.  More options would be
> possible, but I thinks is is already getting impractical.
> 
> 
> Jürgen
> 
> 
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer