On Fri, Jul 22, 2011 at 02:59:09PM +0200, Tollef Fog Heen wrote:
> | How hard can it be to
> | support both sysvinit and systemd? It's just two little files to
> | maintain instead of one. We also have/had both .menu and .desktop
> | files. Sure, they will be out of sync once in a while, but other than
> | that I really don't see the problem.
>
> The problem with this is you get even more combinatorial explosion and
> less testing, particularly for packages that have few users.
I don't see any combinatorial explosion, at most a doubling in effort to
maintain a small part of a package. Less testing, I agree.
(Although I suspect maintainers will just copy&paste systemd config files just
like they copy&paste init scripts, and just tweak it until it runs on their
system, and then just wait for the users to report bugs for all the test
cases they missed.)
> | By the way, we already have the SysV init scripts, so we don't need to
> | do anything to keep supporting that, while it will take some time
> | before every package with a daemon has the required systemd scripts in
> | place, I think we should wait with any switch until there is at least
> | enough coverage.
>
> (Ignoring the kFreeBSD side of things for a bit): Why? As others have
> pointed out, systemd uses sysvinit scripts just fine.
Yes, but some people seem also to be saying that SysV init scripts are hard to
write and buggy, and that one of the benefits of systemd is the easy config
files.
Also, if systemd would use init scripts just fine, then one could argue to just
use SysV init scripts for everything, since then there is no extra effort
involved and people can easily swap init systems.
I don't know, but it seems to me that having half of the daemons use SysV init
scripts and the other half systemd config files is the worst case. For example,
is the dependency information in the LSB headers enough for systemd to order
the starting of those daemons correctly with respect to those who use systemd
natively?
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <guus@debian.org>
Attachment:
signature.asc
Description: Digital signature