All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Mihai Prica <mihai.prica@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] bluez5: Rename tests package to testtools
Date: Fri, 06 Sep 2013 11:14:57 -0700	[thread overview]
Message-ID: <522A1BA1.9020709@linux.intel.com> (raw)
In-Reply-To: <f8bc81b6558ad3b4e6c81403916ca1bfa42b236b.1378477619.git.mihai.prica@intel.com>

On 09/06/2013 07:49 AM, Mihai Prica wrote:
> Bluez5 ships some tools that can be used to test its
> functionality.
>
> The installation can be tested using "make check" and
> this should be included in a ptest package.
>
> [YB #5028]
>
> Signed-off-by: Mihai Prica <mihai.prica@intel.com>
> ---
>   meta/recipes-connectivity/bluez5/bluez5.inc |    6 ++++--
>   1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc b/meta/recipes-connectivity/bluez5/bluez5.inc
> index e2b7169..e5cb9e8 100644
> --- a/meta/recipes-connectivity/bluez5/bluez5.inc
> +++ b/meta/recipes-connectivity/bluez5/bluez5.inc
> @@ -55,7 +55,7 @@ do_install_append() {
>   }
>
>   ALLOW_EMPTY_libasound-module-bluez = "1"
> -PACKAGES =+ "libasound-module-bluez ${PN}-test ${PN}-obex"
> +PACKAGES =+ "libasound-module-bluez ${PN}-testtools ${PN}-obex"
>
>   FILES_libasound-module-bluez = "${libdir}/alsa-lib/lib*.so ${datadir}/alsa"
>   FILES_${PN} += "${libdir}/bluetooth/plugins ${libdir}/bluetooth/plugins/*.so ${base_libdir}/udev/ ${nonarch_base_libdir}/udev/ ${systemd_unitdir}/ ${datadir}/dbus-1"
> @@ -70,7 +70,7 @@ FILES_${PN}-obex = "${libdir}/bluez5/bluetooth/obexd \
>                      "
>   SYSTEMD_SERVICE_${PN}-obex = "obex.service"
>
> -FILES_${PN}-test = "${libdir}/bluez/test/*"
> +FILES_${PN}-testtools = "${libdir}/bluez/test/*"
>
Are all the files located in test related to the testtools or are some 
of them related to ptest?

Sau!

>   FILES_${PN}-dbg += "\
>     ${libdir}/${BPN}/bluetooth/.debug \
> @@ -79,4 +79,6 @@ FILES_${PN}-dbg += "\
>     */udev/.debug \
>     "
>
> +RDEPENDS_${PN}-testtools += "python python-dbus python-pygobject"
> +
>   SYSTEMD_SERVICE_${PN} = "bluetooth.service"
>


      reply	other threads:[~2013-09-06 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06 14:48 [PATCH 0/2] Bluez5 fixes Mihai Prica
2013-09-06 14:49 ` [PATCH 1/2] bluez5: Install the bluetooth library Mihai Prica
2013-09-06 14:49 ` [PATCH 2/2] bluez5: Rename tests package to testtools Mihai Prica
2013-09-06 18:14   ` Saul Wold [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=522A1BA1.9020709@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=mihai.prica@intel.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.