i had to add the following config-option in order to compile zinf without arts: use arts || myconf="${myconf} --disable-arts"
We can add zinf 2.2.1 while we're at it...
I have a 2.2.1 ebuild. I have done 2.2.0 fine without arts. Areyou running KDE? do you have USE=-arts in your make.conf? Also do you just add the line after the use arts && line? Thanks.
Created attachment 5581 [details] zinf-2.2.1.ebuild Update to zinf-2.2.1. No dependancy changes.
I don't run KDE and have -arts in my use-flags. Yes I just added this line after the use arts && myconf ... Sorry it took me so long to answer.
It seems as though zinf 2.2.1 has the arts plugin firmly disabled. No matter what is passed to configure it isn't built by default, and if I force building it, it has an undefined symbol arts_free. I'm committing a zinf-2.2.1 ebuild that has arts support disabled entirely. I'll ask the zinf authors about this.
I uncommented your changes for arts, since I use the arts plugin. I'm also seeing the arts_free error, except if I start zinf through artsdsp: then I don't see the error, and the arts plugin loads fine, and I have it selected. Dunno if that helps, but at least my arts output works.
Reminder to self, do ask the zinf developers...
Dan I have a 2.2.3 I am starting testing now. I have readded basic arts and alsa to test. I have an update musicbrainz ebuild to go along also. I already did gnome/esound/oss with no problems and I am installing arts/alsa .9 now to test.
Sounds good. This is low on my priority list atm beause I'm handling kde proper, following the 3.1 release...
See bug #14859 for Zinf-2.2.3. Worked with arts on my machine so you should be able to close this bug now.
I've added arts support to the 2.2.3 ebuild with some makefile fixes neede to let it build properly. I'll contact zinf upstream about those changes, meanwhile please test the ebuild.
The zinf people didn't reply to either of my 2 emails :-( Anyway this is working now afaik.
