On Sb, 19 iul 14, 07:49:37, The Wanderer wrote: > > Which points out a large part of the problem, right there: most Gnome > programs do not themselves need to interact with systemd itself (or any > component thereof), but due to the dependency chain passing through > Gnome, installing one of those programs will result in installing > systemd. That qualifies them as "package[s] which depend ... indirectly > on systemd ... without real need"; they do not need systemd, but they > indirectly depend on it anyway. > > The problem is that each step of the dependency chain is there for good > reason, at least from the perspective of the developers / maintainers of > that particular package - but the end result is that a program which > does not need systemd is packaged in a way which requires systemd.
That's also one of the reasons I don't even bother anymore to try out Gnome. Last time I did that (and didn't like it) it was just too difficult to un-install it due to circular Depends/Recommends. Why is any of this systemd's fault? Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt
signature.asc
Description: Digital signature
