[GRASS-dev] winGRASS addons - consolidation/fix release needed!!

Helmut Kudrnovsky hellik at web.de
Sat Jul 27 13:59:51 PDT 2019


hi,

actually, there are several complaints that downloading precompiled winGRASS
addons isn't working, see e.g.

https://trac.osgeo.org/grass/ticket/3455#comment:5
https://lists.osgeo.org/pipermail/grass-web/2019-July/004925.html
https://lists.osgeo.org/pipermail/grass-user/2019-July/080557.html
etc.

checked now the situation of download server URLs and related g.extension
code lines regarding several branches and master:

--------------

*grass72

https://wingrass.fsv.cvut.cz/grass72/x86/addons/

[DIR]	grass-7.2.2/	2019-07-07 09:10 	- 	 
[DIR]	grass-7.2.3/	2019-07-07 09:10 	- 	 
[DIR]	latest/	2019-07-07 09:10 	- 	 


https://wingrass.fsv.cvut.cz/grass72/x86_64/addons/

[DIR]	grass-7.2.2/	2019-07-07 09:10 	- 	 
[DIR]	grass-7.2.3/	2019-07-07 09:10 	- 	 
[DIR]	latest/	2019-07-07 09:10 	- 	 

--------------

*grass74

https://wingrass.fsv.cvut.cz/grass74/x86_64/addons/

[DIR]	grass-7.4.svn/	2019-07-25 09:06 	- 	 


https://github.com/OSGeo/grass/blob/releasebranch_7_4/scripts/g.extension/g.extension.py#L937

    base_url = "http://wingrass.fsv.cvut.cz/" \
               "grass%(major)s%(minor)s/%(platform)s/addons/" \
               "grass-%(major)s.%(minor)s.%(patch)s" % \
               {'platform': platform,
                'major': version[0], 'minor': version[1],
                'patch': version[2]}

--------------

*grass76

https://wingrass.fsv.cvut.cz/grass76/x86_64/addons/

[DIR]	grass-7.6.svn/	2019-07-25 09:06 	- 	 
[DIR]	latest/	2019-07-25 09:06 	- 	 

https://wingrass.fsv.cvut.cz/grass76/latest/addons/

[DIR]	grass-7.6.svn/	2019-07-25 09:06 	- 	 
[DIR]	latest/	2019-07-25 09:06 	- 	 


https://github.com/OSGeo/grass/blob/releasebranch_7_6/scripts/g.extension/g.extension.py#L937

    base_url = "http://wingrass.fsv.cvut.cz/" \
               "grass%(major)s%(minor)s/%(platform)s/addons/" \
               "grass-%(major)s.%(minor)s.%(patch)s" % \
               {'platform': platform,
                'major': version[0], 'minor': version[1],
                'patch': version[2]}

--------------

*grass77

https://wingrass.fsv.cvut.cz/grass77/x86_64/addons/

[DIR]	grass-7.7.dev/	2019-07-25 09:06 	- 	 

https://github.com/OSGeo/grass/blob/master/scripts/g.extension/g.extension.py#L1021

    base_url = "http://wingrass.fsv.cvut.cz/" \
               "grass%(major)s%(minor)s/%(platform)s/addons/" \
               "grass-%(major)s.%(minor)s.%(patch)s" % \
               {'platform': platform,
                'major': version[0], 'minor': version[1],
                'patch': version[2]}
				
--------------				

in the MLs there are some suggestions for workarounds, e.g.

in https://trac.osgeo.org/grass/ticket/3455#comment:6

following change is suggested:

base_url = "http://wingrass.fsv.cvut.cz/" \
               "grass%(major)s%(minor)s/%(platform)s/addons/" \
               "grass-%(major)s.%(minor)s.%(patch)s" % \
               {'platform': platform,
                'major': version[0], 'minor': version[1],
                #'patch': version[2]}
                'patch': 'svn'}
		
the same in
https://lists.osgeo.org/pipermail/grass-user/2019-July/080526.html

base_url = "http://wingrass.fsv.cvut.cz/" \
           "grass%(major)s%(minor)s/%(platform)s/addons/" \
           "grass-%(major)s.%(minor)s.%(patch)s" % \
           {'platform': platform,
            'major': version[0], 'minor': version[1],
            #'patch': version[2]} # comment this out
            'patch': 'svn'} # add this
			
--------------	

see e.g.

https://lists.osgeo.org/pipermail/grass-user/2019-July/080561.html

shows that, with the workaround, a GRASS GIS library mismatch issue may
occur.


* for the short term, we need a winGRASS addon consolidation and a fix
release; our winGRASS users seem to use the addons in a regular way

* for the long term, buidling winGRASS addon via appveyor (compare e.g.
https://pdal.io/development/compilation/windows.html) may be another way to
deliver them.

in another thread a discussion started how GRASS GIS should handle addons
after the GIT switch: central repo vs. distributed addon repos.

short and long term ideas/solutions for winGRASS addons mentioned above are
related to the question central repo vs. distributed addon repos.

ideas? suggestions? PRs? 








-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html


More information about the grass-dev mailing list