I can help with the latter, but would you mind submit this (and other) patches to the mainline github project, please.
We should work more closely together with github mainline project.
I submitted a patch to make this build again, I have no desire to claim maintainership. Feel free to decline it if you don't think it is any good.
There are many SUSE only patches because the package was released almost five years ago. The 2.7.5 release has been announced as almost there for years already, so it should be no surprise there are quite a number of patches by now. Also note that quite a few of them have to do with the fact that in (open)SUSE we try to setup the system, where upstream used to leave that to the user. I'm more inclined to follow NUT in that aspect, as I don't think one should try to automate this for such a critical service. These will probably not be accepted upstream anyway.
I don't know what your intentions are with a _service file, but if you mean to track upstream GitHub, you're on your own. I have been one of the core maintainers of NUT several years ago and back then running the development version was absolute madness for a service which is going to require stability. This unlikely is any different today. I certainly wouldn't recommend that.
From version 2.3.0 onwards,
gdlib-configis no longer available in GD, so better usepkg-configwhich is required anyway in order to buildThanks. There are a way too many SUSE only patches. The package should also get a _service file pointing to: https://github.com/networkupstools/nut
I can help with the latter, but would you mind submit this (and other) patches to the mainline github project, please. We should work more closely together with github mainline project.
I submitted a patch to make this build again, I have no desire to claim maintainership. Feel free to decline it if you don't think it is any good.
There are many SUSE only patches because the package was released almost five years ago. The 2.7.5 release has been announced as almost there for years already, so it should be no surprise there are quite a number of patches by now. Also note that quite a few of them have to do with the fact that in (open)SUSE we try to setup the system, where upstream used to leave that to the user. I'm more inclined to follow NUT in that aspect, as I don't think one should try to automate this for such a critical service. These will probably not be accepted upstream anyway.
I don't know what your intentions are with a
_servicefile, but if you mean to track upstream GitHub, you're on your own. I have been one of the core maintainers of NUT several years ago and back then running the development version was absolute madness for a service which is going to require stability. This unlikely is any different today. I certainly wouldn't recommend that.@a_faerber, @duwe, @elvigia, @hreinecke, @lrupp, @michals, @seife, @seilerphilipp, @trenn, @tsaupe: review reminder