Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: alex.kiernan@gmail.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-Core][PATCH v2] packagegroup-base: Add option to set zeroconf provider
Date: Mon, 17 Feb 2025 11:32:11 +0100	[thread overview]
Message-ID: <bbf0cbf2-b188-402e-83d2-f3e6f8dfd300@cherry.de> (raw)
In-Reply-To: <20250215165545.1929-1-alex.kiernan@gmail.com>

Hi Alex,

On 2/15/25 5:55 PM, Alex Kiernan via lists.openembedded.org wrote:
> avahi, systemd-resolved and mDNSResponder (in meta-networking) can all
> provide Zeroconf services. Add a `ZEROCONF_DAEMON` option to select
> which of these will provide service via packagegroup-base-zeroconf.
> 

If I'm not mistaken, this seems to be fitting RPROVIDES usage?

What if we had something like

RPROVIDES:${PN}-resolved += "zeroconf-daemon"

in the systemd recipe

RPROVIDES:${PN}-libnss-mdns += "zeroconf-daemon"

in the mdns recipe and

RPROVIDES:${PN}-daemon += "zeroconf-daemon"

in the avahi-libnss-mdns recipe?

and then we simply RDEPENDS on zeroconf-daemon?

Does that work (haven't tested myself)? What do you think?

Cheers,
Quentin


  reply	other threads:[~2025-02-17 10:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-15 16:55 [OE-Core][PATCH v2] packagegroup-base: Add option to set zeroconf provider Alex Kiernan
2025-02-17 10:32 ` Quentin Schulz [this message]
2025-02-17 11:16   ` Alex Kiernan
2025-02-17 17:05     ` Quentin Schulz
2025-02-17 18:09       ` Alex Kiernan
2025-02-17 18:19         ` Khem Raj
2025-02-18 14:57           ` Alex Kiernan
2025-02-17 23:05     ` Richard Purdie
2025-05-20 13:39 ` Richard Purdie
2025-05-20 14:16   ` Joshua Watt
2025-05-20 15:12     ` Alex Kiernan

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=bbf0cbf2-b188-402e-83d2-f3e6f8dfd300@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=alex.kiernan@gmail.com \
    --cc=openembedded-core@lists.openembedded.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