[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:19 sbl]:
 > Pyhon modules are supposed to use lazy imports and should catch if a
 required python library is available at runtime.

 +1

 > For C modules, installation of libraries through g.extension is probably
 not very straight forward.

 Right. For some addons, we actually have that as an optional dependency in
 the core. However, pip, R, and conda can actually do that, so perhaps if
 we use them in background, they could take care of that.

 There have been suggestions like this in the past, but a lot of changed in
 past years. pip is now basically part of Python. conda is quite common.
 There is a lot of R packages using C++. For example //itzi// is using pip
 rather than g.extension.

 > Silently installing stuff can be a bit scary...

 Why do you think it is scary for GRASS GIS? pip, R, conda, apt, yum, ...
 all install dependencies of a package you asked for. Why this should not
 happen for GRASS GIS?

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