From: "Yu, Mingli" <mingli.yu@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH 2/3] python-pbr: add python-pbr bb
Date: Wed, 29 Jun 2016 16:19:02 +0800 [thread overview]
Message-ID: <57738476.20303@windriver.com> (raw)
In-Reply-To: <CANx9H-BvJ1ONU6ebaEYR8NSaNdYhAioMuMxNmE6ntWTBn7ZBYQ@mail.gmail.com>
On 2016年06月28日 22:56, Tim Orling wrote:
> On Tue, Jun 28, 2016 at 1:36 AM, <mingli.yu@windriver.com> wrote:
>
>> From: Mingli Yu <mingli.yu@windriver.com>
>>
>> * Add python-pbr bb file as python-mock depends on
>> python-pbr-native
>>
>> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
>> ---
>> .../recipes-devtools/python/python-pbr_1.10.0.bb | 22
>> ++++++++++++++++++++++
>> 1 file changed, 22 insertions(+)
>> create mode 100644 meta-python/recipes-devtools/python/
>> python-pbr_1.10.0.bb
>>
>> diff --git a/meta-python/recipes-devtools/python/python-pbr_1.10.0.bb
>> b/meta-python/recipes-devtools/python/python-pbr_1.10.0.bb
>> new file mode 100644
>> index 0000000..4a08bde
>> --- /dev/null
>> +++ b/meta-python/recipes-devtools/python/python-pbr_1.10.0.bb
>> @@ -0,0 +1,22 @@
>> +DESCRIPTION = "Python Build Reasonableness: PBR is a library that injects
>> some useful and sensible default behaviors into your setuptools run"
>> +HOMEPAGE = "https://pypi.python.org/pypi/pbr"
>> +SECTION = "devel/python"
>> +LICENSE = "Apache-2.0"
>> +LIC_FILES_CHKSUM = "file://LICENSE;md5=1dece7821bf3fd70fe1309eaa37d52a2"
>> +
>> +SRCNAME = "pbr"
>> +
>> +SRC_URI = "
>> https://pypi.python.org/packages/source/p/${SRCNAME}/${SRCNAME}-${PV}.tar.gz
>> "
>>
>
> You don't need to do this if you inherit pypi.
Thanks! Update to inherit pypi.
>
>
>> +
>> +SRC_URI[md5sum] = "8e4968c587268f030e38329feb9c8f17"
>> +SRC_URI[sha256sum] =
>> "186428c270309e6fdfe2d5ab0949ab21ae5f7dea831eab96701b86bd666af39c"
>> +
>> +S = "${WORKDIR}/${SRCNAME}-${PV}"
>> +
>> +inherit setuptools
>> +
>> +DEPENDS_class-target += " \
>> + python-pip \
>> + "
>> +
>> +BBCLASSEXTEND = "native"
>> --
>> 2.8.1
>>
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
next prev parent reply other threads:[~2016-06-29 8:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 8:36 [meta-python][PATCH]: update some python packages bb mingli.yu
2016-06-28 8:36 ` [PATCH 1/3] python-mccabe: Remove pytest mingli.yu
2016-06-28 14:55 ` Tim Orling
2016-06-29 8:18 ` Yu, Mingli
2016-06-28 8:36 ` [PATCH 2/3] python-pbr: add python-pbr bb mingli.yu
2016-06-28 14:56 ` Tim Orling
2016-06-29 8:19 ` Yu, Mingli [this message]
2016-06-28 8:36 ` [PATCH 3/3] python-mock: add python-pbr-native dependency mingli.yu
2016-06-28 14:50 ` [meta-python][PATCH]: update some python packages bb Tim Orling
2016-06-29 6:23 ` Yu, Mingli
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=57738476.20303@windriver.com \
--to=mingli.yu@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox