Hi, All packages from my default installation are now free of init.d scripts/insserv usage (at least when the last package maintainers accept and/or submit their packages to Factory finally). I would like to use this opportunity to set an example and make it visible to people, that systemd is the default and init scripts are legacy, deprecated and should be converted to systemd units. Why? If you install a system, you will not have insserv or other tools to activate and run init scripts installed by default anymore. But there is still the /etc/init.d hierachy. So I would like to move that directories to an own RPM, prefereable "insserv-compat". Why "insserv-compat"? And what does this mean for existing packages? - packages having correct insserv requires will not notice this - packages with broken insserv requires, but which builds currently by accident, will continue to build by accident. - packages messing up with their requires and currently don't build, will continue to not build until somebody fixes them. But this is completly independent of this change - rpm will fail to build until either somebody converted rpmconfigcheck to a systemd unit file or we drop it. Opinions? Objections? If nobody has good reasons against this, I will make this change in 2-3 weeks. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org