dbus: Merge dbus-library, dbus-tools and dbus-daemon into a single package#81
dbus: Merge dbus-library, dbus-tools and dbus-daemon into a single package#81rickynils wants to merge 1 commit intoNixOS:masterfrom
Conversation
…ckage. This overcomes problems with circular dependencies between dbus-library and dbus-tools.
|
I think that merging dbus-* is a good idea |
|
They are split to prevent a dependency on X11 in applications that require the dbus libraries. So we shouldn't merge them. In the future we can probably use a single dbus package with multiple outputs to handle this. |
|
Closed, well, but what about the circular dependency, or do we have another solution to the described problem? |
|
Yes, I also wonder what we should do in the meantime... I have Den 2012-08-01 20:52:10 skrev Vladimír Čunát
|
ghc 8.{2,4}: Add patches for deterministic profiling symbols.
Init offlineimap service
Janik-Haag
added
the
12.first-time contribution
clients: Add irssi 0.8.18
5 participants
I ran into a problem where an application (network-manager-applet) tried to execute dbus-launch from /nix/store/...dbus-library.../bin/dbus-launch, which doesn't exist, since the dbus-launch binary is built by the dbus-tools package. It turns out, however, that it is the dbus-library itself that refers to the dbus-launch binary (in its own bin dir). Since dbus-tools depends on dbus-library, this can't be fixed without introducing a circular dependency.
What do you say about merging dbus-library, dbus-tools and dbus-daemon (which already is equal to dbus-library) into one package?
Doing that solves the problem, and doesn't seem to cause any other problems. The only trouble I can imagine, is that some X11 dependencies are introduced in dbus-library: