[GRASS-PSC] Important question about GRASS Mac binaries

Vaclav Petras wenzeslaus at gmail.com
Thu Sep 8 06:12:41 PDT 2022


On Tue, 16 Aug 2022 at 14:00, Michael Barton <Michael.Barton at asu.edu> wrote:

>
> Is there storage for the GRASS project where these can go?
>

They can be uploaded as assets to releases at GitHub, see e.g.:

https://github.com/OSGeo/grass/releases/tag/8.2.0

Having binaries on the development platform seems quite natural, it is done
by other projects, and in the future the whole thing would ideally happen
automatically.

It's not huge but not tiny. Currently at about 13 GB for all. If not, I may
> look into creating an OSF or Zenodo community I can use.
>

There are cases of software binaries at Zenodo:

https://zenodo.org/record/4659370

We are already using Zenodo, so that would make sense. The issued DOIs for
binaries in addition to the source code may cause confusion, though. Zenodo
has a main DOI for a "project" and a DOI for each version of the "project".
The main DOI is a redirect to the latest version. For source code, we have
some confusion there already with latest, because it is latest by release
date, not by version number. This would likely be the same for binaries.

OSF would probably work too, but you won't be using most of its project
management features and I don't know how good it is for simple cases (where
Zenodo works well).

Vaclav
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-psc/attachments/20220908/2ab55e07/attachment.htm>


More information about the grass-psc mailing list