[GRASS-dev] [GRASS GIS] #2132: Create a system for building and running GRASS modules written in Python

[GRASS GIS]

#2132: Create a system for building and running GRASS modules written in Python
-------------------------------------------------------+--------------------
 Reporter:  wenzeslaus                                 |       Owner:  grass-dev@…              
     Type:  defect                                     |      Status:  new                      
 Priority:  normal                                     |   Milestone:  7.0.0                    
Component:  Python                                     |     Version:  svn-trunk                
 Keywords:  makefiles, addons, path, python, packages  |    Platform:  All                      
      Cpu:  All                                        |  
-------------------------------------------------------+--------------------

Comment(by wenzeslaus):

 In r58208, I used `get_lib_path` function to find the `r.modis`
 library/package. This actually fixes `r.modis.import` for me on Ubuntu.
 The `r.modis.download` started successfully before and starts also after
 the change.

 However, the Makefile is still a issue at least for addons. How the
 directories are set and what the `get_lib_path` function tries has unclear
 system. There is a module group name `r.modis` (name of directory in
 source code) and than there is a library (which is supposed to be a Python
 package?) name `libmodis`. However, `libmodis` is renamed to `r.modis`
 when installed and libraries (or whatever) from one module group are
 grouped to the same directory named by module group. So, the result is
 `r.modis/r.modis` directory in `GRASS_ADDON_BASE` (e.g.,
 `/home/john/.grass7/addons/r.modis/r.modis`).

 Grouping the libraries makes sense to avoid potential conflicts. For few
 libraries it is not necessary but I can imagine a groups of modules in
 addons which includes some 3rd party library into the distribution. Then
 grouping is advantage. The renaming seems strange to me. Is there some
 reason for it?

 I'm not sure where the other than Python files related to the module or
 module group should go. This is the case of ''resources'' such as XMLs or
 images. I'm not sure if there is some mechanism for it now.

 The terminology started to be a real issue here, I'm not sure how to speak
 about things. Addon, extension, package, library, GRASS module, Python
 module, module group, module package...

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2132#comment:3>
GRASS GIS <http://grass.osgeo.org>