From: akuster808 <akuster808@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2][dizzy] python-nose: backport it to dizzy
Date: Sun, 14 Jun 2015 16:12:24 -0700 [thread overview]
Message-ID: <557E0A58.7010809@gmail.com> (raw)
In-Reply-To: <CAMKF1sqHATLXo8i55Z+MjFdfb=Ra-pCYR8h=jjtgxGp5e36ewA@mail.gmail.com>
On 6/14/15 9:13 AM, Khem Raj wrote:
> On Sun, Jun 14, 2015 at 1:56 AM, akuster808 <akuster808@gmail.com> wrote:
>> Alejandro,
>>
>> This looks to be a new recipe. I don't believe dizzy is taking new features.
> Contextual. If its a leaf recipe in terms of dependencies, I don't see any harm.
It is still a new recipe. If adding new recipes is something that
should be allowed on a maintenance release, then the policy should be
updated. I still not in favor of adding new recipes nor features to a
maintenance release.
- Armin
>
>> - armin
>>
>>
>> On 06/08/2015 06:56 AM, Alejandro Hernandez wrote:
>>> Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
>>> ---
>>> meta/recipes-devtools/python/python-nose_1.3.6.bb | 16 ++++++++++++++++
>>> 1 file changed, 16 insertions(+)
>>> create mode 100644 meta/recipes-devtools/python/python-nose_1.3.6.bb
>>>
>>> diff --git a/meta/recipes-devtools/python/python-nose_1.3.6.bb
>>> b/meta/recipes-devtools/python/python-nose_1.3.6.bb
>>> new file mode 100644
>>> index 0000000..d6e8fc1
>>> --- /dev/null
>>> +++ b/meta/recipes-devtools/python/python-nose_1.3.6.bb
>>> @@ -0,0 +1,16 @@
>>> +DESCRIPTION = "nose extends the test loading and running features of
>>> unittest, \
>>> +making it easier to write, find and run tests."
>>> +SECTION = "devel/python"
>>> +LICENSE = "LGPLv2.1"
>>> +LIC_FILES_CHKSUM = "file://lgpl.txt;md5=a6f89e2100d9b6cdffcea4f398e37343"
>>> +
>>> +SRC_URI =
>>> "http://pypi.python.org/packages/source/n/nose/nose-${PV}.tar.gz"
>>> +
>>> +SRC_URI[md5sum] = "0ca546d81ca8309080fc80cb389e7a16"
>>> +SRC_URI[sha256sum] =
>>> "f61e0909a743eed37b1207e38a8e7b4a2fe0a82185e36f2be252ef1b3f901758"
>>> +
>>> +S = "${WORKDIR}/nose-${PV}"
>>> +
>>> +inherit setuptools
>>> +
>>> +BBCLASSEXTEND = "native nativesdk"
>>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2015-06-14 23:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 13:56 [PATCH 0/2][dizzy] python-nose and python-contextlib backports to dizzy Alejandro Hernandez
2015-06-08 13:56 ` [PATCH 1/2][dizzy] python-contextlib: backport " Alejandro Hernandez
2015-06-14 5:52 ` akuster808
2015-06-08 13:56 ` [PATCH 2/2][dizzy] python-nose: backport it " Alejandro Hernandez
2015-06-14 5:56 ` akuster808
2015-06-14 16:13 ` Khem Raj
2015-06-14 23:12 ` akuster808 [this message]
2015-06-15 11:42 ` Otavio Salvador
2015-06-09 0:37 ` [PATCH 0/2][dizzy] python-nose and python-contextlib backports " akuster808
2015-06-09 10:01 ` Paul Eggleton
2015-06-09 22:19 ` Alejandro Hernandez
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=557E0A58.7010809@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.