Bug#727708: init system coupling etc.
]] Colin Watson
> So, in my amendment, I intended this to be the "cooperating groups of
> packages intended for use with specific init systems", which language I
> think I borrowed from your proposal. If logind-208 Depends: systemd (or
> indeed if it's part of systemd), then that's fine, as long as it doesn't
> end up being required by something else that isn't so intimately related
> to the init system; in other words, a dependency on systemd doesn't
> become any less a dependency on systemd just because it happens to be
> spelled "Depends: logind" and there's only one provider available.
To be honest, I'm not sure why init systems are being singled out
here. It's not really feasible to run both kdm and gdm at the same time,
or run multiple window managers at the same time or a whole host of
other software. Or would you be as strongly opposed to having a tool
(say an accessibility tool) depend on GDM because it provided interfaces
that KDM doesn't? (I'm not sure this is actually true, but I could
easily see it being true.)
I also find it curious how A depending on interface B provided by
packages C and D becomes RC buggy because D is unmaintained and gets
removed from the archive. It's not how we usually treat bugs.
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are