From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Guillaume Chaye <guillaume.chaye@zeetim.com>
Cc: buildroot@buildroot.org, Eric Le Bihan <eric.le.bihan.dev@free.fr>
Subject: Re: [Buildroot] [PATCHv2 1/2] package/avahi: add missing dependency.
Date: Wed, 5 Feb 2025 17:17:07 +0100 [thread overview]
Message-ID: <20250205171707.725b3989@windsurf> (raw)
In-Reply-To: <20250127091711.3877692-1-guillaume.chaye@zeetim.com>
Hello,
On Mon, 27 Jan 2025 10:17:10 +0100
Guillaume Chaye <guillaume.chaye@zeetim.com> wrote:
> libavahi-client is not built if dbus is not installed.
>
> Signed-off-by: Guillaume Chaye <guillaume.chaye@zeetim.com>
> ---
> package/avahi/Config.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/avahi/Config.in b/package/avahi/Config.in
> index 728bc4fdd1..ae53aaf156 100644
> --- a/package/avahi/Config.in
> +++ b/package/avahi/Config.in
> @@ -39,6 +39,7 @@ config BR2_PACKAGE_AVAHI_DAEMON
> config BR2_PACKAGE_AVAHI_LIBAVAHI_CLIENT
> bool
> default y if BR2_PACKAGE_DBUS
> + select BR2_PACKAGE_DBUS
I understand your idea, but this is not what this option is about. This
option is not a typical visible option, with a prompt in menuconfig to
enable/disable avahi-client.
Instead it's a blind option that other packages can observe (but not
select!) to know if libavahi-client will be available or not.
And indeed, as soon as D-Bus is enabled,
BR2_PACKAGE_AVAHI_LIBAVAHI_CLIENT becomes true, telling other packages
that libavahi-client will be there.
So your PATCH 2/2 needs to select BR2_PACKAGE_AVAHI and
BR2_PACKAGE_DBUS, which will ensure libavahi-client gets built.
The problem with having an option is that we can't disable it. So if we
make it a visible option, and a user keeps it disabled... we have no
way to tell avahi to not build libavahi-client: as soon as D-Bus is
there, libavahi-client will be built.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-02-05 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 9:17 [Buildroot] [PATCHv2 1/2] package/avahi: add missing dependency Guillaume Chaye
2025-01-27 9:17 ` [Buildroot] [PATCHv2 2/2] package/sane-airscan: add new package Guillaume Chaye
2025-02-05 16:17 ` Thomas Petazzoni via buildroot [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=20250205171707.725b3989@windsurf \
--to=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=guillaume.chaye@zeetim.com \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.