rse there are still a lot of bug reports *in* -shim, i. e. which
hit when you run with sysvinit or upstart. But that's the opposite
case of what you were concerned about, right?
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Deb
for a fair
while in Ubuntu (even in our 14.04 LTS) without too many problems. So
my feeling is that we can certainly stabilize -shim by the jessie
release. (We need to do that anyway, as we need to support sysvinit
regardless of what we do on upgrades/new installs.)
Thanks,
Martin
--
Marti
that. In that sense we already
support classic sysvinit and startpar, but they don't use different
startup scripts in packages.
> If your real point is "pick systemd *or* upstart and don't try to
> assert that we should support both", I can easily agree with that.
That
t as long as
we have non-Linux ports. So this is already 2, and that at least still
has some technical justification. But having more than $DEFAULT and
sysv just boils down to "we can't make a decision".
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.
oughly equivalent in terms of what a
desktop environment needs from it). polkit is a different beast and is
*not* deprecated; it has been switched over to use logind for checking
"is that process on an active foreground console", which it previously
used ConsoleKit for.
Martin
ter to continously test startup
scripts for thousands of packages. So "I would expect the community
for that init system to do the work" is not a plan; it's a vague hope
at best and not realistic at all in my opinion.
Martin
--
Martin Pitt| http://www.piwa
6 matches
Mail list logo
