Stefan,

here is a quick explanation

The paths are not hardcoded on the first install. Instead, Processing
tries to find those dependencies (which usually works fine in osgeo4w
distributions),or lets the user configure them manually. Once they are
configured manually (as you have done), that value is stored as a
setting (and written to the ini file for further uses). If you change
your QGIS version or Processing version, the configuration is not
changed, so it will use that value again and again (and since it is
already configured, a new version of Processing wont try to find those
dependencies).

The only solution to that is to have different ini files and specify
which one to use in each case, using the --configpath option

Cheers

2016-01-25 12:54 GMT+01:00 Blumentrath, Stefan <[email protected]>:
> Hi Alex,
>
> Thanks for your reply, and sorry if my question was a bit unclear...
>
> When I want to use e.g. GRASS 7 in Processing, I have to provide the path to 
> the "GRASS7 folder" in Processing --> Processing Options --> Providers
> From there, in my case e.g. "C:\Program Files (x86)\QGIS 
> Lyon\apps\grass\grass-7.0.3RC2" has been saved as an absolute path to my 
> QGIS.ini file in my home directory.
>
> If I use different QGIS versions in parallel (e.g. latest stable and LTR) the 
> path can change. Furthermore, I have to update it manually, after each update 
> of GRASS or SAGA (because then the paths change as well...
>
> This is what I meant, not the source code...
>
> But maybe it would be better to have the paths themselves more stable...
> Recently, Helmut Kudrnovsky did some work on making RStudio available in the 
> GRASS console in OSGeo4W. Maybe something like this is needed to grab the 
> path to GRASS, SAGA or R for processing...?
>
> Cheers
> Stefan
>
>
> -----Original Message-----
> From: Alexander Bruy [mailto:[email protected]]
> Sent: 25. januar 2016 12:13
> To: Blumentrath, Stefan <[email protected]>
> Cc: [email protected]
> Subject: Re: [Qgis-developer] Processing provider versions and hard coded 
> path in settings
>
> Hi Stefan,
>
> Processing providers are just plugins, so they installed in the global QGIS 
> plugins directory. There is no hadrcoding in Processing sources related to 
> the providers.
>
> 2016-01-25 12:04 GMT+02:00 Blumentrath, Stefan <[email protected]>:
>> Dear devs,
>>
>>
>>
>> In my QGIS.ini, the paths to the Processing providers are hard coded,
>> which means I have to manually adjust them after every software update
>> (Saga, GRASS, R).
>>
>> Any chance to pass the updates to the user(s)`s QGIS settings (or make
>> QGIS recognizing the Processing providers installed together with
>> QGIS), or is this only a limitation of the --configpath solution?.
>>
>>
>>
>> Should I extend:
>>
>> http://hub.qgis.org/issues/12623
>>
>> (as it seems related) or should I open a new ticket (in case this
>> wanted and feasible of course)...
>>
>>
>>
>> Kind regards,
>>
>> Stefan
>>
>>
>>
>>
>> _______________________________________________
>> Qgis-developer mailing list
>> [email protected]
>> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> --
> Alexander Bruy
> _______________________________________________
> Qgis-developer mailing list
> [email protected]
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
Qgis-developer mailing list
[email protected]
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to