From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/avahi: enable libavahi-client support
Date: Mon, 03 Nov 2014 12:31:54 +0100 [thread overview]
Message-ID: <1415014314.2065.4.camel@posteo.de> (raw)
In-Reply-To: <87ioix43oc.fsf@dell.be.48ers.dk>
Peter, All,
On So, 2014-11-02 at 23:51 +0100, Peter Korsgaard wrote:
> >>>>> "J?rg" == J?rg Krause <jkrause@posteo.de> writes:
>
> > Some packages needs libavahi-client support which is autobuild by avahi if
> > avahi-daemon and dbus is selected. To select libavahi-client explicitly makes
> > this dependency more obvious for dependent packages.
>
> > libdns_sd is only build by avahi if libavahi-client is present (and
> > `--enable-compat-libdns_sd` is set as configure option). So it's safe to
> > depend on libavahi-client instead of avahi-daemon.
>
> Having a user visible option for this is a bit odd as it cannot be used
> to DISABLE the library.
>
> Perhaps it should just be a hidden helper option for other packages
> instead? (so drop the bool and help text)
I agree with you.
I want to check for libavahi-client in shairport-sync.mk without adding
a user prompt in Config.in:
ifeq ($(BR2_PACKAGE_AVAHI_LIBAVAHI_CLIENT),y)
SHAIRPORT_SYNC_DEPENDENCIES += avahi
SHAIRPORT_SYNC_CONF_OPTS += --with-avahi
else
SHAIRPORT_SYNC_CONF_OPTS += --with-tinysvcmdns
endif
Does it make sense to have a hidden config symbol which is both
selectable and checkable. This is what I have in mind:
config BR2_PACKAGE_AVAHI_LIBAVAHI_CLIENT
bool
default y if (BR2_PACKAGE_AVAHI_DAEMON &&
BR2_PACKAGE_DBUS)
depends on BR2_PACKAGE_AVAHI_DAEMON
select BR2_PACKAGE_DBUS
# selected in package A
select BR2_PACKAGE_AVAHI_LIBAVAHI_CLIENT
# checked in package B
ifeq ($(BR2_PACKAGE_AVAHI_LIBAVAHI_CLIENT),y)
Best regards
J?rg
prev parent reply other threads:[~2014-11-03 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 0:10 [Buildroot] [PATCH 1/1] package/avahi: enable libavahi-client support Jörg Krause
2014-11-02 22:51 ` Peter Korsgaard
2014-11-03 11:31 ` Jörg Krause [this message]
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=1415014314.2065.4.camel@posteo.de \
--to=jkrause@posteo.de \
--cc=buildroot@busybox.net \
/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