Re: [GRASS-dev] grass-addons on github

The main advantage of having all grass-addons in one repo is that they are easy to manage (for core devs). The main disadvantage of having all grass-addons in one repo is that a contributor concerned about his single addon needs to get the whole repo, wasting disk space. There are probably two di

Re: [GRASS-dev] [GRASS GIS] #3851: r.out.mpeg always fails because the output file name is empty

#3851: r.out.mpeg always fails because the output file name is empty --+ Reporter: paoloz | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: Component: Raster |Versi

[GRASS-dev] (no subject)

Hi devs I just did a completely fresh install of grass 7.6.2. The whole compilation is completed without issues. But when starting grass up, I am getting the following message. GRASS 7.6.2svn (nc_spm_08_grass7):~ > ERROR 1: libgrass_raster.7.5.svn.so: cannot open shared object file: No such file

Re: [GRASS-dev] grass-addons on github

Hi, Collecting addons in a central repo seems very valuable to me too, for all the reasons Vacslav mentioned. I am no git expert either, but PRs should not be a big issue to do (unless you are VERY productive). People could merge their own PRs, no? Creating a PR, does not mean it has to be rev

Re: [GRASS-dev] grass-addons on github

On Fri, May 24, 2019 at 3:57 PM Anna Petrášová wrote: > > > On Fri, May 24, 2019 at 3:55 AM Martin Landa > wrote: > >> Hi, >> >> pá 24. 5. 2019 v 8:48 odesílatel Paulo van Breugel >> napsal: >> > I have read about the procedure for contributors to the main grass >> repository. Question is, how

Re: [GRASS-dev] grass-addons on github

On Fri, May 24, 2019 at 3:55 AM Martin Landa wrote: > Hi, > > pá 24. 5. 2019 v 8:48 odesílatel Paulo van Breugel > napsal: > > I have read about the procedure for contributors to the main grass > repository. Question is, how are we going to deal with add-ons? > > > > Are we working with a centra

Re: [GRASS-dev] grass-addons on github

On Fri, May 24, 2019 at 2:48 AM Paulo van Breugel wrote: > > Are we working with a central repository (OSGeo/grass-addons) and follow > the same protocol as for OSGEO/grass. If so, who will be responsible for > approving pull requests? An alternative more like the old situation is that > authors

Re: [GRASS-dev] [GRASS GIS] #3852: PyGRASS GridModule silently ignores when module has no output defined

#3852: PyGRASS GridModule silently ignores when module has no output defined --+- Reporter: martinl | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.6.2 Component: PyGRASS

[GRASS-dev] [GRASS GIS] #3852: PyGRASS GridModule silently ignores when module has no output defined

#3852: PyGRASS GridModule silently ignores when module has no output defined -+- Reporter: martinl | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.6.2 Component: PyGRASS |

Re: [GRASS-dev] grass-addons on github

Hi, pá 24. 5. 2019 v 9:54 odesílatel Martin Landa napsal: > in my opinion requesting PRs for `grass-addons` is maybe overkill. It > must be somehow discussed anyway. If we suggest direct commits it's > important to avoid not needed 'merge from master' commits [1]. The > workflow must be clear (re

Re: [GRASS-dev] install addons/extensions on GRASS

Hi, pá 24. 5. 2019 v 8:07 odesílatel Paulo van Breugel napsal: > I was afraid that would be the case. Is there any way to get the executables > and install them manually? last successful build (from 18/5) seems to be still available [1]. Ma [1] https://wingrass.fsv.cvut.cz/grass76/x86_64/addo

Re: [GRASS-dev] grass-addons on github

Hi, pá 24. 5. 2019 v 8:48 odesílatel Paulo van Breugel napsal: > I have read about the procedure for contributors to the main grass > repository. Question is, how are we going to deal with add-ons? > > Are we working with a central repository (OSGeo/grass-addons) and follow the > same protocol