[arch-dev-public] [systemd] adding service files to normal packages?
Hi guys, I started using systemd, on my laptop and plan to expand the usage on my other machines. The experience is good, but quite a lot of packages misses the systemd service files. Most stuff is provided by arch-units package from community. What I need is rpcbind, nfs, ssh, mysql, saned, xinetd, ntp, samba. My opinion on this is, the service files should belong to the packages and not to the arch-units package. Are there any objections in adding such files to the packages? Any other opinions? Thanks for your input. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Hi Tobias,
On Thu, Apr 12, 2012 at 9:07 AM, Tobias Powalowski
What I need is rpcbind, nfs, ssh, mysql, saned, xinetd, ntp, samba.
FWIW, I have some patches for rpcbind to get proper systemd integration, I just need to resubmit them upstream. I think our ssh units could also go upstream to openssh.
My opinion on this is, the service files should belong to the packages and not to the arch-units package.
I agree with this. The arch-units stuff was always just meant as a temporary solution (and it is definitely sub-optimal). We have been enabling unit files in the individual packages wherever these are available upstream, but I guess the time has come to include unit files for (at least some of) the remaining packages in the same way we now include rc scripts. Cheers, Tom
participants (2)
-
Tobias Powalowski
-
Tom Gundersen