Summary: | net-irc/xchat-xsys needs audacious built with dbus support | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | elprespufferfish |
Component: | New packages | Assignee: | Tony Vroon (RETIRED) <chainsaw> |
Status: | VERIFIED INVALID | ||
Severity: | minor | CC: | phatboye |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
elprespufferfish
2008-01-25 00:19:08 UTC
eerror "Unsupported configuration: D-Bus disabled" ewarn "D-Bus has been disabled. Note that audtool will not be provided, you will not" ewarn "be to able to get song information from scripts or control the player remotely." ewarn "This configuration is provided for people heavily opposed to D-Bus that are able " ewarn "to live with the loss of functionality that this implies. Reports about remote " ewarn "control or multiple instances of Audacious being launched will be *closed*." As clearly announced in the audacious ebuild, this bug report will be closed. If you disagree with the functionality provided by the dbus USE-flag, please take it up with the reporter and commenter on bug #199069. Note that these warnings *will* have been displayed on your terminal as portage buffers these messages and will display them at the end of a merge. May I suggest that the xchat-xsys ebuild be altered to notify the user to rebuild audacious with dbus support if it wasn't enabled initially? if built_with_use --missing true media-sound/audacious dbus ; then eerror "You MUST build media-sound/audacious with the dbus USE flag" Something like that? Unsupported. That means it is not supported. As such, you do not file bugs about it. The message will have been displayed clearly on your screen. If you do not agree with having this USE-flag, bug #199069 has the contact details of the people you'll want to talk to. Closing. *** Bug 208606 has been marked as a duplicate of this bug. *** Why don't you enable the flag by default via EAPI-1? *** Bug 208606 has been marked as a duplicate of this bug. *** |