![](https://seccdn.libravatar.org/avatar/71f3f43ecafb2a6e2dba1f3c378ba5ae.jpg?s=120&d=mm&r=g)
On Friday, 17 March 2017 10:22 Thorsten Kukuk wrote:
On Fri, Mar 17, Michal Kubecek wrote:
On Friday, 17 March 2017 9:55 Thorsten Kukuk wrote:
The correct Requires depends on, in which pre/post install sections you are calling insserv. But normally, "Requires(pre)" is correct and "Requires:" is wrong. Because you use insserv already in a %pre* section, so insserv needs to be installed before your package will be installed.
Would that also prevent anything included in %{insserv_prereq} from being uninstalled after I install my package? My understanding of your earlier mail was that after your change, it is responsibility of any package with init scripts to make sure at least insserv-compat is installed whenever my package is installed.
It is the responsibility of any package calling packages in pre/post install sections that they are installed. Independent of if this is insserv or any other tool. That's the case since SUSE supports pre/post install scripts.
So packages calling insserv in there pre/post install section and not making sure that it is installed are buggy and did only work by accident in the past, because other, correct packages did install it.
I guess I wasn't clear enough earlier. I understand why having the dependency "Requires(pre): %{insserv_prereq}" is _needed_. My question rather is if it is going to be _sufficient_ even after /etc/init.d becomes part of insserv-compat and is no longer automatically present. There is a check that unless a directory under which my package installs files is one of the "known to be always there", it should be either in my package or in one of its Requires. Michal Kubeček -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org