From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] zeroconf/avahi USE flag
Date: Tue, 04 Nov 2008 12:11:56 -0500 [thread overview]
Message-ID: <4910825C.7090304@gentoo.org> (raw)
Hey all,
A few ebuilds treat things differently with regard to this situation and
it really needs to get rectified.
net-misc/ntp
zeroconf? ( || ( net-dns/avahi net-misc/mDNSResponder ) )
net-print/cups
zeroconf? ( !avahi? ( net-misc/mDNSResponder ) )
avahi? ( net-dns/avahi )
kde-base/kdelibs
!avahi? ( !bindist? ( net-misc/mDNSResponder !kde-misc/kdnssd-avahi ) )
avahi? ( kde-misc/kdnssd-avahi )
To name a few... the above will cause blockers for people depending on
their merge order if they have the following in their USE flags.
USE="zeroconf -avahi"
Maybe we should clean the whole thing up and do like net-misc/ntp does
it. Thoughts?
reply other threads:[~2008-11-04 20:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4910825C.7090304@gentoo.org \
--to=cardoe@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@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