Am 18.01.2015 um 12:17 schrieb Raymond Wooninck:
On Sunday 18 January 2015 11:11:10 Michal Kubecek wrote:
In particular, this part:
This is a very ridiculous statement, sorry.
The package maintainers will not be 'pushed' to drop it. Nor will any scripts ensure there are no initV scripts. That's just pure non-sense
I guess that only Dominque can answer what his intentions were, however what I have seen so far is again a big flame war against systemd.
No. It's a big flame war against broken promises. Even though I personally only have technical problems with systemd and personal problems with some of its developers (or more precise: with their attitude, to a point where I refuse to work on the project, but that's a different story), I deeply understand Michal's concerns as apparently he remembers the discussion of late 2012 the same as I do: "of course you will not be forced, everything will still work, yada yada". And -- probably also the same as Michal -- I did not believe a single word back then. But still I would have appreciated to be proved wrong.
My understanding from Tomas is that he just wants to implement a rpmlint message that indicates that the package does not contain any systemd scripts despite that it has a number of init scripts. Nowhere it has been said that the package is not allowed to have initscripts, just that openSUSE would like to move on and ensure that every package that has initscripts also has systemd unit files.
Read the subject of this thread: "...failing build of packages with initscripts...", try to digest its meaning, then come back to this discussion. Sorry, but the topic here is "forbidding init scripts in openSUSE", not "print a polite message if an init script is found". -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org