Addons on Windows update

It appears that the addons for Windows have not been updated since the 9th of February. Is that right?

Could maybe @martinl take a look?

Hi devs,

GRASS provides a very convenient mechanism to install addons via g.extension. On Linux systems, this includes the flexibility to install addons from local files or alternative GitHub repositories. However, this flexibility is not available on Windows.

As a result, Windows users are effectively dependent on a single server. When this repository is updated less frequently, it can delay access to new features or fixes. It also makes it difficult to distribute addons for testing purposes or for niche use cases that do not justify inclusion in the main repository.

I am therefore wondering what possible alternatives there are to provide/distribute addons. Perhaps supporting multiple addon sources (e.g., allowing g.extension to query alternative or backup servers)? Or making it possible to install from local files on Windows, or providing a lightweight tool or addon that allows users to install addons from distributed packages addons (like the official Windows addons)?

I guess I could create a small addon that takes zipped addons (in any case Python addons) and installs them (there is probably the issue of adding it to internal list of addons, would have to look into that as well). But that feels like a makeshift solution (certainly if I were to make it - but still, it could provide a solution).

I am curious how others are dealing with this (if at all).

Hi Paulo. I also think that the state of Windows addons is an important issue.

For Python addons, my current work-around is simply to download the addon and launch it in as a script, skip g.extension entirely.

I understand that the C addons need compiling and build tools may not readily be available. Will the transition to CMake help? Currently custom urls are disabled for g.extension on Windows, because addons from custom sources can’t be compiled. The Python addons, however, do not really need compiling, even for their documentation. So, how about enabling custom urls in g.extension for Python addons on Windows?