version bump for media-sound/ario to 1.4.1 Reproducible: Always
Created attachment 212467 [details] ario-1.4.1.ebuild Ario 1.4.1 introduces several new dependencies, which are in this ebuild. One possible problem is that it seems to require avahi unconditionally, despite the configure.ac checks that indicate it's optional. The compile fails every time if the avahi libraries aren't on the system; passing --disable-avahi has no effect. I've contacted upstream about this possible bug, and in the meantime I removed the zeroconf/avahi USE checks from the ebuild. It now has a hard dependency on avahi. Other changes: the required gtk+ version has moved to 2.16, libunique is now required, and the mpd flag controls whether or not Ario uses the system libmpdclient or if it uses its embedded copy. Also enabled the configure switches for playlists and the search function. Probably everyone will want these, and there are no external libraries they depend on.
well, I'd rather not bump this in the tree if the hard-dependency was a mistake, so waiting for upstream action on this
(In reply to comment #2) > well, I'd rather not bump this in the tree if the hard-dependency was a > mistake, so waiting for upstream action on this > I got a response back from upstream: *** I have tried to compile Ario without avahi support on my computer (Ubuntu 9.10): I removed all avahi libraries: *sudo aptitude remove libavahi-client-dev libavahi-common-dev libavahi-glib-dev ./configure && make* : Fails because avahi is missing (avahi is activated by default) * ./configure --disable-avahi && make *: Successfully builds. Avahi libraries are only required if '--disable-avahi' is not used. You can check it at the end of configure display, you should have: Avahi support is: DISABLED *** So upstream says it IS optional, but I can't get it to actually be disabled in the ebuild I posted, nor in the old one with the $(use_enable zeroconf avahi) line and zeroconf in IUSE. Your mileage may vary -- try editing the ebuild to that on your machine and see if it does any better.
Actually, I've tried it today and didn't hit that issue. 1.4.1 in the tree with a slightly different ebuild
Veriosn bump to 1.4.4 - do I really need to open new bug? ;)
