I removed the "enable-dbus" in audacious-1.4.0.ebuild and changed "enable-dbus" to "disable-dbus" in audacious-plugins-1.4.0.ebuild and both packages build fine and do work for me. As i dont need nor want remote control for audacious, i dont need this dbus dependency and it would be nice, if this gets optional so i can change this by use-flag without using extra local packages. Reproducible: Always
*** This bug has been marked as a duplicate of bug 197894 ***
eh 1. this is not rc1, this is for the not masked 1.4.0 2. it does not fail to compile, it does work without dbus installed (at least the same as with dbus enabled and installed) 3. why should not the user decide if he uses remote control with dbus or not?
Because people filed me bugs saying that audtool didn't work and it implied that they expected this to work by default. If you reach consensus with the reporter of the other bug, let me know and we can revisit.
(In reply to comment #4) > Because people filed me bugs saying that audtool didn't work and it implied > that they expected this to work by default. If you reach consensus with the > reporter of the other bug, let me know and we can revisit. > As it happens some of the functionality i needed required compiling with dbus for Audacious 1.4, however i do agree that users should be given the choice, which was why i opened the call initially.
Here is the answer of the reporter, he also says, dbus is only needed for some (optional) functionality and not the main functions itself, so i reopen this bug for a revisit.
Note that both audacious & audacious-plugins will need to be compiled with USE="dbus" for remote control to work and that I will close any further bugs about remote control not working with "enable D-Bus" RESO INVA. Sign your agreement and I'll add 1.4.0-r1 with more USE-flags.
That is ok for me.
Addressed in 1.4.2, now in portage.
