Rhythmbox mt-daapd dependency issues [SOLVED]

Baly · n00b Joined: 04 Oct 2006 Posts: 10

Not sure if this belongs here or in multimedia as it seems to affect both however here it goes. All rhythmbox ebuilds post 0.10.1 no longer allow you to use daap and howl useflags without using avahi. Mt-daapd requires mDNSResponder which conflicts with avahi. The only way I was able to run rhythmbox with daap support and actually run a daap server was to mask all rhythmbox packages >media-sound/rhythmbox-0.10.1. Is this an error in the ebuild (ie overlooked) or is there a way around this I was unable to find?

strider1551 · n00b Joined: 26 Nov 2007 Posts: 4

I am stuck in this mess as well. Upon reviewing the dependencies http://gentoo-portage.com/media-sound/rhythmbox/Dep#ptabs, it appears that some changes were made to the use flags. In 0.10.1, there was an avahi use flag. After that version, the avahi flag disappears and the daap flag appears, which apparently pulls in avahi as a dependency. I don't know enough about use flags and ebuilds, but it looks like avahi was simply renamed daap.

I tried emerging without the daap flag. The result was that rhythmbox did not have the daap sharing plugin. Since I'm away from the campus on winter break, I'm not sure if my own music is still being shared, even if rhythmbox won't show it.

My guess is that the way we enabled daap sharing is no longer the recommended way. Here's to hoping that someone who knows what is going on fills us in.

Baly · n00b Joined: 04 Oct 2006 Posts: 10

The avahi use flag was added to mt-daapd preventing the need for mDNSResponder and resolving the conflict.