From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Painted into a corner: avahi and mDNSResponder
Date: Sun, 12 Oct 2008 10:34:03 +0200 [thread overview]
Message-ID: <200810121034.03757.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <e38d12ff0810120125x31020621sa281cd5e1b36f46f@mail.gmail.com>
On Sunday 12 October 2008 10:25:51 Andrey Vul wrote:
> On Sun, Oct 12, 2008 at 3:51 AM, Alan McKinnon <alan.mckinnon@gmail.com>
wrote:
> > On Sunday 12 October 2008 08:04:22 Volker Armin Hemmann wrote:
> >> On Sonntag 12 Oktober 2008, Alan E. Davis wrote:
> >> > Almost perpetually, the following packages or their versions are
> >> > blocking. I have run emerge -e system several times. Some other
> >> > problems were cleared up, and this
> >> > avahi--mDNSResponder/mdnsresponder-compat whatever it all is, just
> >> > keeps coming back even when solved by some skullduggery. I've removed
> >> > both of them at one time or another.
> >> >
> >> > [blocks B ] net-dns/avahi ("net-dns/avahi" is blocking
> >> > net-misc/mDNSResponder-107.6-r5)
> >> >
> >> > [blocks B ] net-misc/mDNSResponder ("net-misc/mDNSResponder" is
> >> > blocking net-dns/avahi-0.6.23)
> >> >
> >> > I guess the problem is that I am running gnome and also have two or
> >> > three different versions/slots of kde installed. I suppose, then,
> >> > it's remarkable that only these blocks are showing up?
> >> >
> >> > Can someone lend a hand on this? Anything I do is little more than
> >> > blind tinkering.
> >> >
> >> > Alan
> >>
> >> set the avahi useflag, unmerge mdnsresponder, emerge avahi.
> >
> > That looks familiar. I remember similar deep blocks myself - it was nasty
> > at the time.
> >
> > For the OP's benefit, here's a high level summary of what is going on:
> >
> > Avahi and mDNSResponder implement a system called ZeroConf, first
> > designed by Apple. It's a way for machines on a network to find each
> > other and what network features they support. These systems are quite
> > low-level so unfortunately the implementations are often incompatible.
> >
> > By and large you will find that Gnome stuff supports Avahi and KDE stuff
> > supports mDNSResponder, so the only way out of this mess is often
> > extensive use of 'equery hasuse', 'equery depends' and 'emerge -pvt' so
> > see what pulls in what. But first you should research what these things
> > are so you can make intelligent decisions about what to include and what
> > to drop. The thing that cleared it up for me was an interview with the
> > KDE team lead responsible for these features - Google will find it for
> > you.
>
> IIRC mdnsresponder-compat USE flags allows use of avahi in KDE (3).
I believe you are correct:
alan@nazgul ~ $ grep mdns /var/portage/profiles/use.*
/var/portage/profiles/use.local.desc:net-dns/avahi:mdnsresponder-compat -
Enable compat libraries for mDNSResponder
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2008-10-12 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 2:30 [gentoo-user] Painted into a corner: avahi and mDNSResponder Alan E. Davis
2008-10-12 3:07 ` Andrey Vul
2008-10-12 6:04 ` Volker Armin Hemmann
2008-10-12 7:51 ` Alan McKinnon
2008-10-12 8:25 ` Andrey Vul
2008-10-12 8:34 ` Alan McKinnon [this message]
2008-10-12 9:11 ` Volker Armin Hemmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200810121034.03757.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox