Hi Alex,
On 2/17/25 12:16 PM, Alex Kiernan wrote:
On Mon, Feb 17, 2025 at 10:32 AM Quentin Schulz
<quentin.sch...@cherry.de> wrote:
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?
I guess I'm guilty of copying what was there (WIRELESS_DAEMON)
Fair enough, consistency is probably better here then :)
and then we simply RDEPENDS on zeroconf-daemon?
Does that work (haven't tested myself)? What do you think?
And then selection via a PREFERRED_RPROVIDER:zeroconf-daemon = "..."
I guess I think it should work, though my concern is the interaction
between the daemon and the nss plugin, which is how I ended up down
this rabbit hole in the first place!
We seem to have very little usage of RPROVIDES (other than as a
migration mechanism) and PREFERRED_RPROVIDER in general.
That makes sense if the packages are absolutely incompatible with each
other. For example, for the WIRELESS_DAEMON case, you may want to have
wpa-supplicant but probably could have iwd too in the same rootfs and
let the user pick the one they want to use?
If we can have multiple zeroconf daemons, then that wouldn't be a good
solution anyways.
Cheers,
Quentin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#211546):
https://lists.openembedded.org/g/openembedded-core/message/211546
Mute This Topic: https://lists.openembedded.org/mt/111202159/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
