Description of problem: Let's get the ball rolling on this one... http://fedoraproject.org/wiki/Features/SysVtoSystemd https://fedoraproject.org/wiki/Packaging:Guidelines:Systemd https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 546898 [details] Native systemd service file for edac.service
Aristeu, any objection to my making this change?
No objection but I don't have time to work on this right now. how soon you want this in?
Ideally early in the f18 timeframe, but I'm willing to do it, if you like.
Note that the window is open to at least beta to introduce ( I think Tom went bit further than that last development cycle ) units into the release so preferably build this for F17 and ofcourse rawhide
I should mention once that window is closed so is the ability to introduce units into the GA distribution as in units cannot be introduce as an updated to GA release without explicit granted permission from FESCO. Some maintainers have been bitten by this policy as in legacy sysv initscript is broken due to various reasons in F15 and users file bugs left and right but native systemd unit works perfectly in F16 and the maintainer cant really fixed it in F15 since he cant introduce the native systemd unit into that release. Note that this policy was NOT set by the systemd crew and generally is disliked amongst them.
So I can go ahead?
Yep, please. I started reading about how it works, but ended up being pulled for something else.
Done, thanks all!