Hi Mike,
I'm a bit surprised you haven't got any replies yet; Either nobody
seems to care, or else nobody else seems to use avahi.
You might be better off emailing cshore [1] directly as he committed r27479.
Failing that, you can email thepeople [2] and offer to be the avahi
maintainer. Then
Hi Jon. Thanks for the pointers. Yeah, I was a tiny bit surprised to hear
nothing. I didn't know how to contact the committers, TBH. Are you a maintainer
yourself?
Mike
On 8 Nov 2011, at 17:43, Jonathan McCrohan wrote:
Hi Mike,
I'm a bit surprised you haven't got any replies yet; Either
Hi,
On Tue, Nov 8, 2011 at 6:46 PM, Mike Brady mikebr...@eircom.net wrote:
Hi Jon. Thanks for the pointers. Yeah, I was a tiny bit surprised to hear
nothing. I didn't know how to contact the committers, TBH. Are you a
maintainer yourself?
I will try to fix it. From your experience, can you
Hi. Here is the list:
avahi-autoipd -- doesn't depend on DBUS at all, it's the only DBUS don't care.
libavahi, avahi-daemon, avahi-dnsconfd -- can be DBUS-enabled or not.
avahi-utils, libavahi-client -- these require DBUS.
If avahi-utils or libavahi-client is selected, then the DBUS-enabled
Hi everybody.
This is a long note, and it's about the avahi package. It's about changes made
in Changeset 27479 (June 7, 2011). Sorry not to have commented earlier, but I
was busy on a separate project.
To come directly to the point, and with respect, I think that Changeset 27479
is flawed
