From: akuster808 <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][v2][PATCH] cpuset: add new python package
Date: Wed, 22 Jun 2016 17:52:23 -0700 [thread overview]
Message-ID: <576B32C7.6090209@gmail.com> (raw)
In-Reply-To: <1466025817-30091-1-git-send-email-akuster@mvista.com>
Ping.
I don't see this in the patch queue, was it removed, dropped or did I
mess up the submittal? Did I miss a response ?
regards,
Armin
On 06/15/2016 02:23 PM, Armin Kuster wrote:
> Signed-off-by: Armin Kuster <akuster@mvista.com>
> ---
> .../recipes-devtools/python/python-cpuset_1.5.7.bb | 23 ++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
> create mode 100644 meta-oe/recipes-devtools/python/python-cpuset_1.5.7.bb
>
> diff --git a/meta-oe/recipes-devtools/python/python-cpuset_1.5.7.bb b/meta-oe/recipes-devtools/python/python-cpuset_1.5.7.bb
> new file mode 100644
> index 0000000..8f6532c
> --- /dev/null
> +++ b/meta-oe/recipes-devtools/python/python-cpuset_1.5.7.bb
> @@ -0,0 +1,23 @@
> +SUMMARY = "Cpuset is a Python application to make using the cpusets facilities in the Linux kernel easier"
> +SECTION = "devel/python"
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
> +
> +SRCNAME = "cpuset"
> +
> +SRC_URI = "https://github.com/lpechacek/${SRCNAME}/archive/v${PV}.tar.gz"
> +
> +SRC_URI[md5sum] = "6ad79b26ba03f559604d74513cc34392"
> +SRC_URI[sha256sum] = "32334e164415ed5aec83c5ffc3dc01c418406eb02d96d881fdfd495587ff0c01"
> +
> +S = "${WORKDIR}/${SRCNAME}-${PV}"
> +
> +inherit distutils
> +
> +RDEPENDS_${PN} = "\
> + python-core \
> + python-re \
> + python-logging \
> + python-textutils \
> + python-unixadmin \
> + "
>
next parent reply other threads:[~2016-06-23 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1466025817-30091-1-git-send-email-akuster@mvista.com>
2016-06-23 0:52 ` akuster808 [this message]
2016-06-23 4:17 ` [meta-oe][v2][PATCH] cpuset: add new python package Paul Eggleton
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=576B32C7.6090209@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-devel@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.