From: "Guðni Már Gilbert" <gudni.m.g@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v4 6/6] recipes-connectivity: Drop dbus from RDEPENDS:${PN}
Date: Tue, 01 Apr 2025 07:35:07 -0700 [thread overview]
Message-ID: <27416.1743518107824629818@lists.openembedded.org> (raw)
In-Reply-To: <20250401140430.13837-6-niko.mauno@vaisala.com>
[-- Attachment #1: Type: text/plain, Size: 189 bytes --]
BlueZ depends on dbus at runtime. Shouldn’t the recipe therefore explicitly list it in RDEPENDS? It seems weird to me to have the dependency come from a RRECOMMENDS in different recipe.
[-- Attachment #2: Type: text/html, Size: 204 bytes --]
next prev parent reply other threads:[~2025-04-01 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 14:04 [PATCH v4 1/6] default-providers: Add VIRTUAL-RUNTIME_dbus variable Niko Mauno
2025-04-01 14:04 ` [PATCH v4 2/6] dbus: Allow using dbus-lib with alternative D-Bus Niko Mauno
2025-04-01 14:04 ` [PATCH v4 3/6] dbus-glib: Revise RDEPENDS:${PN}-tests assignment Niko Mauno
2025-04-01 14:04 ` [PATCH v4 4/6] systemd: Support using alternative runtime D-Bus Niko Mauno
2025-04-01 14:04 ` [PATCH v4 5/6] glib: " Niko Mauno
2025-04-01 14:04 ` [PATCH v4 6/6] recipes-connectivity: Drop dbus from RDEPENDS:${PN} Niko Mauno
2025-04-01 14:35 ` Guðni Már Gilbert [this message]
2025-04-01 15:50 ` [OE-core] " Ross Burton
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=27416.1743518107824629818@lists.openembedded.org \
--to=gudni.m.g@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 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.