Log file Viewer

[03:00:41] <dstufft> njs: ngoldbaum meanmicio that behavior is expected

[03:39:48] <njs> dstufft: oh right, because there's only one release, duh

[19:22:51] <FichteFoll> what would be a good way to distribute a systemd unit in my python package? (using setuptools)

[19:23:03] <FichteFoll> bbiab

[19:24:35] <ngoldbaum> and it needs to be installed into a system path?

[19:53:56] <FichteFoll> well, ireally it should go to /usr/lib/systemd/user (depending on the specified prefix)

[19:56:52] <ngoldbaum> so there's https://stackoverflow.com/questions/35448758/using-setup-py-to-install-python-project-as-a-systemd-service

[19:57:00] <ngoldbaum> but i tend to agree with mikko ohtomaa's comment

[19:57:07] <ngoldbaum> Python packages themselves should stay neutral as possible and do not force any systemd manipulation which imply root priviledges during setup.py run. What happens if user wants to install your package to a virtualenv for development? Instead, I suggest your application ships with a separate script in bin which can do systemd installation

[19:57:38] <ngoldbaum> or they're next comment

[19:57:43] <ngoldbaum> Alternatively build a package for your operating system (deb, rpm, etc.) as that's the right place to put operating system specific installation commands.

[20:06:08] <FichteFoll> thanks for taking a look. I agree with this