Package request: am, or appman

Package name

am

Package homepage

https://github.com/ivan-hc/AM

Description

I know about #26702, but it would seem upstream is still reluctant to decouple from systemd.

am is 4 years old, stable, still maintained, and to be sure I have tried it out and the functionality works on Void.
I know this ecosystem is not ideal. I don't like having to manage distro packages, flatpaks and appimages seperately. But flatpaks are incredibly space inefficient, and often this kind of packaged software in flatpaks/appimages won't meet the void package requirements because they may not be compiled.

Just a trivial example: Joplin v3.2.12 appimage is 216 MB, compared to joplin on a fresh instance of flatpak which takes up 3.5 GB in /var/lib/flatpak. As far as I understand, a major drawback of appimages is the difficulty in updating which this proposal ameliorates.

am is the system version, appman is the user-only version. I am only requesting am, I include the other name here just so this can be searched/recognised more easily. It's just shell scripts, i.e. not compiled, but there is a strong argument it would be useful to many users.

Upstream is kind enough to provide instructions for distro maintainers to use it as well.

Does the requested package meet the package requirements?

System

Is the requested package released?

Yes

Start by reading the upstream AM instructions for Linux distro maintainers and the package conventions in the Void source packages collection. Check how the am shell scripts should be represented as a Void package, then verify that the resulting package is available and meets the issue's stated system-package requirements.