Based on https://github.com/jotyGill/openpyn-nor … emd.py#L35 I presume the only actually complex bit is the ExecStart... which is invoking the openpyn program itself. This could likely even be handled via an EnvironmentFile with OPTIONS=... and requiring no modification to the service file (which merely invokes `ExecStart=/usr/bin/openpyn $OPTIONS`)
]]>It seems the premise is the edits the user would need to make (to a drop-in) are complex enough that this tool exists to generate the content. So user's of this tool would not be using `systemctl edit` to modify the drop-in anyways. Unless of course they did that and just copy-pastaed the content this tool generates.
]]>Specifically, the openpyn (https://aur.archlinux.org/packages/openpyn-nordvpn/) package will install /etc/systemd/system/openpyn.service, but not as part of the normal installation process.
It does so when the end user runs openpyn --init. However, I think the package should still own the file and the package should remove the file on uninstall.
Create the file in package() and if the user needs to edit it, it should be edited as a drop-in file (e.g. systemctl edit).
Consider submitting a pull request to upstream to do this properly.
Consider also fixing stupidities like WorkingDirectory= being the directory in which the python module is installed to site-packages.
]]>Specifically, the openpyn (https://aur.archlinux.org/packages/openpyn-nordvpn/) package will install /etc/systemd/system/openpyn.service, but not as part of the normal installation process.
It does so when the end user runs openpyn --init. However, I think the package should still own the file and the package should remove the file on uninstall.