Yamaban wrote:
On Wed, 3 Apr 2013 09:20, Ludwig Nussel
wrote: Stephan Kulow wrote:
On 02.04.2013 10:06, Michal Kubecek wrote:
On Fri, Mar 29, 2013 at 11:29:22PM -0300, Cristian Rodríguez wrote:
Does anyone have access to a full unpacked tree of factory and can post what packages contain init scripts but not service files so I can take look at them ? there is no rpmlint check for that :-|
And not long ago I was being assured there won't be...
We agreed not to enforce that. So your fine to have a package with init scripts. But it's perfectly fine also to have a rpmlint warning that a package has *only* init script and Cristian adding systemd services for them - if the maintainer of the package disagrees to add it, then we can talk again.
Well, the truth is that it doesn't make much sense anymore to keep the sysv scripts if there is a service file. It only adds potential code duplication and confusion. So I'd vote for having either .service files or init scripts in a package but not both. However, adding service files that break previous features or just add the init script shell code 1:1 as ExecStartPre should be avoided too.
As long as there is a SLE(S|D) without systemd support you are shooting your own legs if you just "drop" all replaced sysVinit scripts.
When I said 'keep the sysv scripts' I was referring to having them installed in the system if %suse_version >= 1230. The package maintainer is free to keep the scripts in the package sources and install them only if the package is used as backport of course. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org