[GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons

[GRASS GIS]

#2895: Define dependencies for GRASS addons
--------------------------+-------------------------
  Reporter:  pmav99       |      Owner:  grass-dev@…
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Milestone:  7.8.3
 Component:  Default      |    Version:  unspecified
Resolution:               |   Keywords:  g.extension
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-------------------------

Comment (by wenzeslaus):

 Replying to [comment:23 sbl]:
 > I just added a draft for a python script that could take care of
 dependencies in Python (conda not tested) and R packages. Other
 dependencies (e.g. C-libraries, commandline tools) are just checked,
 neither loading of the libraries not installation is supported at the
 moment (not sure if the latter is realistic).

 The current code looks straightforward and perhaps worth trying it in
 action (you can make an addon module which installs dependencies and then
 runs g.extension on the actual module).

 However, I think this can also get really complex. What about turning this
 the other way around and focusing supporting GRASS modules which are
 Python packages installed with conda or pip like itzi? They would just use
 the existing systems for dependencies. Still, g.extension could use
 handle_dependencies.py logic, but it would use it to install the module
 rather than the dependencies.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/2895#comment:25>
GRASS GIS <https://grass.osgeo.org>