[GRASS-dev] GRASS in OSGeo4W and upcoming releases

[Stefan Blumentrath]

Dear all,

In the light of upcoming releases (7.8.6 rather soon, 8.0 not too far either) I have been wondering about the (future) availability of GRASS versions on MS Windows.

The Next Generation of OSGeo4W seems to be here, as the download-link on trac.osgeo4w.org already points to it. That is great as it allowed to have an ever growing amount of packages (let alone the large proj-data package) in a comprehensive installer.

Going forward I have ported our github actions on Windows to OSGeo4W-NG (V2) (some cleanup and review remains), so we can test PRs against this new environment.

But my questions are now: on the website we have for three versions advertised for download on Linux (https://grass.osgeo.org/download/linux/): a current, a legacy and a preview version.
Personally, I think we should offer the same on MS Windows, where 7.8 would become the legacy version, 8 the stable version and 8.x the preview once 8.0 is released. For 7.8 and 8.0 we will have release candidates I guess, where we need to decide how we want those in OSGeo4W (should e.g. 8.0.1RC be a new version in grass-stable). The preview version would probably be something like a weekly or nightly build....?
Or is there some naming policy in OSGeo4W we should follow, Jürgen?

I would be willing to contribute to packaging additional versions for OSGeo4w by adjusting the current packaging recipe to other version, oriented on e.g. the different QGIS packages.
Would that be helpful, Jürgen, or would you prefer other ways to help getting this stuff into OSGeo4W-NG? BTW, on what system do you run the code here: https://github.com/jef-n/OSGeo4W (Cygwin? MSYS2?) would be useful to know for testing locally...

Once we have those new versions in OSGeo4W, we should probably also have a look at the addon-builds for Windows. If they run on top of the available GRASS verions in OSGeo4W, we could make sure that addons for the respective versions are available. Builds could be automated in GitHub actions, I guess... I can contribute there as well, but we need an agreed-upon plan first, no?

Any thoughts?

Cheers
Stefan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20210822/a3a37639/attachment.html>