Bugzilla Bug 130297

It seems that banshee needs to check for 'built_with_use net-dns/avahi dbus'
when emerging with USE=daap, otherwise

checking for AVAHISHARP... configure: error: Package requirements (avahi-sharp)
were not met.
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively you may set the AVAHISHARP_CFLAGS and AVAHISHARP_LIBS environment
variables
to avoid the need to call pkg-config.  See the pkg-config man page for
more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/banshee-0.10.9-r1/work/banshee-0.10.9/config.log

!!! ERROR: media-sound/banshee-0.10.9-r1 failed.
Call stack:
  ebuild.sh, line 1532:   Called dyn_compile
  ebuild.sh, line 929:   Called src_compile
  banshee-0.10.9-r1.ebuild, line 99:   Called gnome2_src_configure
  gnome2.eclass, line 51:   Called econf '--enable-avahi' '--disable-xing'
'--disable-helix' '--disable-docs' '--with-gstreamer-0-10' '--enable-ipod'
'--enable-njb' '--disable-gtk-doc'
  ebuild.sh, line 527:   Called die

!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if
relevant.

Works fine when avahi is emerged with USE=dbus though

no, you need avahi to be build with mono use flag according to your log.

 checking for AVAHISHARP... configure: error: Package requirements
(avahi-sharp)
were not met.

You'd have thought so, but it was built with USE=mono.

I've tried it multiple times, it works with USE="mono dbus", and fails with
USE="mono -dbus"

In fact, the banshee ebuild already checks that avahi is built with USE=mono,
but I think it does so incorrectly.

USE="-mono -daap" emerge avahi banshee fails because avahi is built without
mono support, but banshee shouldn't care in this case.

In my opinion the check should be 
if use daap && ! built_with_use net-dns/avahi mono dbus, 
but you're obviously welcome to disagree.

(! built_with_use cat/pkg flag1 flag2 seems to behave in the correct way, but
I'm not 100% sure)

Actually, I think this is an avahi bug, not a banshee bug.

When I do USE="mono -dbus" emerge avahi, part of the output at the end of
autoconf running is

Building avahi-sharp:               no

Which is presumably not the corrent behaviour


I think what I said about the check for avahi being built with mono needing a
'use daap &&' still stands though

(sorry for all the emails bugzilla's sending you)

add avahi maintainer to look at this.

Yep, avahi needs dbus for mono support, I'll fix this later today when I'm back
at home.

Looks like avahi has been fixed, but banshee will still fail if you do

USE="-mono -daap" emerge avahi banshee 

Could you fix that (unless you think that it's the correct behaviour) and then
this can be marked as fixed.

The solution I'm talking about is to change

        if ! built_with_use net-dns/avahi mono ; then

to

        if use daap && ! built_with_use net-dns/avahi mono ; then

(we don't want to be failing because of something to do with avahi when we
aren't supposed to be using it)

i understand what you meant but mono use flag doesn't exist on banshee. It only
makes sense if you add USE="daap" for banshee. USE="-daap -mono" emerge banshee
works for me.

Thanks for the heads up.

USE=-mono emerge avahi && USE=-daap banshee, then :)

i added your changes to the ebuild after get the problem. Thanks!