All installations of rhythmbox >0.10.1 require avahi with daap support enabled. As a result this conflicts with mt-daapd resulting in a system which can either run mt-daapd or rhythmbox with daap support but not both. Rhythmbox-0.10.1 would allow -avahi daap use flags to use the mDNSResponder that comes with mt-daapd. With rhythmbox-0.10.1 being removed from portage it is no longer even possible to build the old version and have a system with both. Reproducible: Always Steps to Reproduce: 1. emerge mt-daapd 2. USE="daap" emerge rhythmbox 3. Actual Results: [ebuild N ] media-sound/rhythmbox-0.11.2-r1 USE="daap dbus hal mad python vorbis -debug -doc -flac -ipod -keyring -libnotify -lirc -musicbrainz -tagwriting" 3,454 kB [blocks B ] net-dns/avahi (is blocking net-misc/mDNSResponder-107.6-r5) [blocks B ] net-misc/mDNSResponder (is blocking net-dns/avahi-0.6.22-r1) Expected Results: rhythmbox with daap support utilizing the mDNSResponder rather than Avahi for daap.
Not a bug per se, but mt-daapd could be using avahi like everyone else. I have no idea how hard this change is, but it'd be worth investigating.
given there is a compat layer in avahi it should be an easy fix. just kick upstream :)
Last I checked, the mDNSResponder compat layer in Avahi had some trouble with mt-daapd (the ~arch version) making it impossible to run more than one mt-daapd instance at once on a system, which is required to advertise files on different filesystems with that version. I think Lennart changed his mind on the task of the compat layers since then, so he might have fixed it, or be ready to fix it.
Avahi compatibility is now within the mt-daapd ebuild, this is now resolved.
