On Mon, Apr 02, 2012 at 06:49:24PM +0100, Simon McVittie wrote: > On 02/04/12 18:03, Andrey Rahmatullin wrote: > > What I meant is: it is a common knowledge that you need to write > > an initscript for each specific distro even though most of them use > > sysvinit, but does this apply to systemd unit files too?
> dbus has a different init script for each distro, but one > (upstream-supplied) systemd unit is shared between at least Fedora and > Debian. I believe this is typically true in other projects. > Most of the differences between Fedora and Debian init scripts aren't > visible in a systemd unit, because they're things like whether to use > daemon(1) or start-stop-daemon or something else, which systemd > sidesteps by not needing either. But it's a real stretch to say that providing those systemd units upstream makes a serious difference in maintenance overhead for distros. Either systemd units, like upstart jobs, are easy to write once and require minimal ongoing maintenance; or they aren't and that's a pretty big strike against systemd. Furthermore, the kinds of things that *will* require changes to job/unit files - such as dependency changes - are very likely to be driven by distros in response to local integration needs. So I don't buy the claims that systemd units upstream are somehow a significant advantage of systemd over upstart. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120402182031.gb11...@virgil.dodds.net
