From: akuster808 <akuster808@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [warrior][PATCH] dbus-test: Improve ptest dependencies dependencies
Date: Sun, 9 Jun 2019 07:36:48 -0700 [thread overview]
Message-ID: <24b25992-6da5-d4c5-0a67-748133e0f74a@gmail.com> (raw)
In-Reply-To: <20190609075658.688-1-Martin.Jansa@gmail.com>
On 6/9/19 12:56 AM, Martin Jansa wrote:
> From: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> The dbus-test package is empty, move its dependencies to the ${PN}-ptest
> package. Also ensure that it doesn't depend on the empty ${PN} package
> which is about to start causing image failures in the following commit.
> In this case the correct dependency is dbus itself.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
got it
thanks
Armin
> ---
> meta/recipes-core/dbus/dbus-test_1.12.12.bb | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-core/dbus/dbus-test_1.12.12.bb b/meta/recipes-core/dbus/dbus-test_1.12.12.bb
> index f4131926c2..486a996879 100644
> --- a/meta/recipes-core/dbus/dbus-test_1.12.12.bb
> +++ b/meta/recipes-core/dbus/dbus-test_1.12.12.bb
> @@ -7,7 +7,6 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=10dded3b58148f3f1fd804b26354af3e \
>
> DEPENDS = "dbus glib-2.0"
>
> -RDEPENDS_${PN} += "make"
> RDEPENDS_${PN}-dev = ""
>
> SRC_URI = "http://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.gz \
> @@ -78,6 +77,7 @@ do_install_ptest() {
> sed -i -e 's;@PTEST_PATH@;${PTEST_PATH};g' ${D}${PTEST_PATH}/run-ptest
> }
>
> -RDEPENDS_${PN}-ptest += "bash"
> +RDEPENDS_${PN}-ptest += "bash make dbus"
> +RDEPENDS_${PN}-ptest_remove = "${PN}"
>
> PRIVATE_LIBS_${PN}-ptest = "libdbus-1.so.3"
prev parent reply other threads:[~2019-06-09 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 7:56 [warrior][PATCH] dbus-test: Improve ptest dependencies dependencies Martin Jansa
2019-06-09 14:36 ` akuster808 [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=24b25992-6da5-d4c5-0a67-748133e0f74a@gmail.com \
--to=akuster808@gmail.com \
--cc=martin.jansa@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