On Tuesday, April 23, 2013 23:04:21 Dirk Müller wrote:
Hi AJ,
I've started adding systemd service files to quantum (taking what Fedora has) and noticed that their setup is different from ours, especially they have many more service files than we have have init ones.
I don't think there is such a difference. the .init files are templates that are generating the actual init files during %install phase. Which is also the main reason why I would discourage your approach.
Ah, I see. Yes, the same approach might be usable for the service files as well...
BTW, the user parameter is wrong in your service files (yes, copying blindly from Fedora does not adhere to suse packaging standards), I've
You looked much further than I did ;)
not looked further on the diff. I don't think this duplication is going to lower our effort of maintaining the packages, and since systemd can perfectly well work with init scripts and our main *target* is to support a non-systemd distribution, I personally don't see the benefit of using something that can only become rotten and broken over time.
BTW is it documented why the review team believes packages that will at no point in time end up on SLE12 are discouraged to be submitted to Factory? That seems to be the first thing that stood out from the decline comment for me.
Dirk, there will be a point in time when SUSE Cloud is based on SLE 12 which is going to use systemd . Adding service files early will not harm us but is not a hard requirement: https://en.opensuse.org/openSUSE:Packaging_guidelines#Init_scripts Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org