Webmin: Standalone installer for module

[NJRoadfan]

If a user installs Netatalk via a package manager, there is currently no way to cleanly install a pre-configured Webmin module. This is only possible when building from source. Right now, the tarball on the site is pre-configured for macOS. If one downloads the Webmin module tarball, they have to manually configure the paths to the daemons and the proper init system start/stop commands before use.

[rdmark]

Right, the tarball gets a macOS configuration because I prepare the releases on a Mac. Good call out.

Do you have an idea how to solve this? Some kind of shell script for the end user that modifies the config file on the fly?

[NJRoadfan]

A shell script can parse the output of netatalk -v to determine the install path of the daemons. Figuring out the init system in use would be a bit more tricky. Obviously this is easy to determine when compiling from source because either meson autodetects it, or the user manually configures it.

[rdmark]

This was the same conundrum I faced when I first started looking into the webmin module. There's quite a lot of complexity to detecting init system and correct paths. Meson does it so nicely for us.

Maybe a "most common" use case default can be applied when packaging the tarballs, i.e. systemd and /usr/local prefix...

[rdmark]

I updated the release process with a few more meson options when building the webmin module tarball. This should give us a better default baseline for starters.

https://github.com/Netatalk/netatalk/wiki/Release-Process

[rdmark]

I uploaded a new 4.1.1 webmin module tarball with the better default configurations.