Hi Martin, Yes, it is indeed not necessarily related.
But what about the idea to provide addon-zip-files for download that could be generated in a make routine (make zip, like e.g. here: https://stackoverflow.com/questions/28844155/makefile-generating-zip-files-of-all-sub-folders and then make copy, like e.g. here: https://stackoverflow.com/questions/19509718/how-to-write-a-makefile-to-copy-scripts-to-server)? Cheers Stefan ________________________________ Fra: Martin Landa <landa.mar...@gmail.com> Sendt: fredag 6. september 2019 21:51:52 Til: Stefan Blumentrath <stefan.blumentr...@nina.no> Kopi: Sebastiaan Couwenberg <sebas...@xs4all.nl>; grass-dev@lists.osgeo.org <grass-dev@lists.osgeo.org> Emne: Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support Hi, pá 6. 9. 2019 v 9:24 odesílatel Stefan Blumentrath <stefan.blumentr...@nina.no> napsal: > People interested in accessing addon code instantly should be able to deal > with the full addon repo. Maybe splitting up grass7 and grass6 addons in > different repos could reduce the pain a bit? I was thinking to split grass7 and grass6 into different branches. grass7/ -> master/grass7 branch grass6/ -> grass6 branch But it's unrelated to discussed g.extension issue. Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev