El Fri, 25 de Jul 2014 a las 8:47 AM, Josh Triplett
<j...@joshtriplett.org> escribió:
Martin Steigerwald wrote:
Sure I can go through setting up chroot for that, yet I really
think if my
work requires changes in other packages and the recent systemd
changes do require this kind of work, I *help* with these changes,
instead of uploading my changes to unstable *before* the other
packages have been fixed.
One point of clarification: systemd does not require changes in
systemd-shim or cgmanager. systemd runs just fine with no such
changes.
Those packages exist for people who for whatever reason don't want to
run systemd, and that's not something the systemd folks should be
expected to help with (any more than people who don't want to run
systemd would be expected to work on systemd).
The systemd maintainers already held systemd 204 back in unstable for
months waiting for the alternative to become viable.
It's not reasonable to expect every systemd upgrade in
unstable/testing
to wait for an alternative init system to keep up. If it does keep
up,
great; there's no fundamental reason to *not* want that alternative to
work. If it doesn't, oh well.
I agree, but would also add that other packages in Debian should at
least try to keep support for other init systems by not depending on
later logind's until systemd-shim is updated. It is clear (I think)
that there are a number of reasons somebody would prefer to use an
alternative init system (including a few unresolved bugs so far), and
packages like GNOME or policykit should support more than just
systemd-sysv.
--
Cameron Norman
