Today I compiled kdelibs using avahi-0.6.2 with the mdnsresponder-compat use-flag set instead of the mDNSResponder ebuild. It compiled and linked without problems. If upstream doesn't include direct support for avahi in future versions, it would be nice to have the dependency on mDSNResponder in kdelibs changed in the way avahi could be used. What do you think?
That it does not work, already tried.
You're right. It doesn't work out of the box. The kdnssd-avahi package from http://helios.et.put.poznan.pl/~jstachow/pub/ is needed. Compilation was a bit of a problem (usual qt/3 problems), but it works or at least "zeroconf:/" in konqueror works.
I hope I do not get on your nerves, but I tried it and also made an ebuild for kdnssd-avahi and it seems to work perfectly. What was the problem, when you tried it?
Created attachment 76520 [details] kdnssd-avahi-0.1.2.ebuild This is the ebuild for kdnssd-avahi, which replaces mDNSResponder with avahi support in kde.
Okay it might work with the other package then :) For sure, it wasn't working out of the box. But I'd rather wait to see what upstream says, kdnssd-avahi is in playground, that means "no support from upstream".
Created attachment 81356 [details] kdnssd-avahi-0.1.2.ebuild 'need-kde 3.5' needs to be inside the function src_compile() otherwise emerge looks for kde v0.1.2 and not kde v3.5
Comment on attachment 81356 [details] kdnssd-avahi-0.1.2.ebuild My patch doesn't work either. There is an issue with the need-kde command. Outside the src_compile function (as in the original ebuild) I get the error: emerge: there are no ebuilds to satisfy "~kde-base/kdelibs-0.1.2". (dependency required by "kde-base/kdnssd-avahi-0.1.2" [ebuild]) With it inside the src_compile function (as with my patch) I get the error: + make install DESTDIR=/var/tmp/portage/kdnssd-avahi-0.1.2/image/ destdir=/var/tmp/portage/kdnssd-avahi-0.1.2/image/ make: *** No rule to make target 'install'. Stop. ... !!! died running make install, kde_src_install:make !!! if you need support, post the topmost build error, and the call stack if relevant. If i remove 'need-kde 3.5' all together then the libraries get installed to /usr/lib instead of the required /usr/kde/3.5/lib/ (a manual copy seems to fix everything)
Created attachment 85330 [details] kdnssd-avahi-0.1.2.ebuild Fixed the ebuild, hopefully someone that knows the kde eclass better than me can make this prettier, but it works now.
Created attachment 85331 [details, diff] kdelibs-3.5.2-r4.ebuild_kdnssd-avahi.diff Here's a patch to the kdelibs-3.5.2-r4 ebuild that has the proper dependencies for kdnssd-avahi.
Created attachment 85337 [details] kdnssd-avahi-0.1.2.ebuild Forgot to handle the arts and kdeenablefinal USE flags.
(In reply to comment #9) > Created an attachment (id=85331) [edit] > kdelibs-3.5.2-r4.ebuild_kdnssd-avahi.diff > > Here's a patch to the kdelibs-3.5.2-r4 ebuild that has the proper dependencies > for kdnssd-avahi. > Should the last part of that patch read: if (use zeroconf || use avahi); then myconf="${myconf} --enable-dnssd" else myconf="${myconf} --disable-dnssd" fi
(In reply to comment #11) > Should the last part of that patch read: > > if (use zeroconf || use avahi); then > myconf="${myconf} --enable-dnssd" > else > myconf="${myconf} --disable-dnssd" > fi > No, because that would use the zeroconf support built into kdelibs instead of the avahi support the new kdnssd-avahi package provides.
Created attachment 87773 [details, diff] kdelibs-3.5.2-r6_kdnssd-avahi.patch Patch against the kdelibs-3.5.2-r6 ebuild to support kdnssd-avahi
Is there any chance to get Avahi support integrated into the 3.5.4 ebuils? As the KDE team is concentrating on KDE4 now, chances that kdnssd-avahi will be included in kdelibs3 or whatever are IMO pretty low. Updated DEPENDs to allow avahi would be cool, I'd test the avahi-enabled ebuilds :) I'm not sure, but I think this <http://bugs.kde.org/show_bug.cgi?id=134212> patch will be needed.
I've found that USE=mdnsresponder-compat makes little difference to KDE's use of Avahi, it seems to ignore it regardless. That said, with the kdnssd-avahi package, all is happy. Is it worth poking upstream again on this? I run a dual-stack IPv4/IPv6 network, and as long as mDNSResponder lacks IPv6 support, I cannot use it on my network.
I'll be taking care of this as soon as I have time, but right now is likely to be next week..
Will take care of it now, although the kdnssd-avahi ebuild I rewrote for the most part.
Thanks Nathan, all in portage now :)
(In reply to comment #18) > Thanks Nathan, all in portage now :) > So that's the correct way to do that. Much simpler :) Good to see this is in portage now!
