From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/3] python: mark the tests modules as special when updating the manifest
Date: Fri, 28 Sep 2018 17:06:15 +0100 [thread overview]
Message-ID: <20180928160616.6672-2-ross.burton@intel.com> (raw)
In-Reply-To: <20180928160616.6672-1-ross.burton@intel.com>
We manually maintain the tests package's content and dependencies, so mark is as
special (matching create_manifest3.py).
Signed-off-by: Ross Burton <ross.burton@intel.com>
---
meta/recipes-devtools/python/python/create_manifest2.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python/create_manifest2.py b/meta/recipes-devtools/python/python/create_manifest2.py
index 1af1443f476..87999991d73 100644
--- a/meta/recipes-devtools/python/python/create_manifest2.py
+++ b/meta/recipes-devtools/python/python/create_manifest2.py
@@ -137,7 +137,7 @@ for key in old_manifest:
# Handle special cases, we assume that when they were manually added
# to the manifest we knew what we were doing.
print ('Handling package %s' % key)
- special_packages=['misc', 'modules', 'dev']
+ special_packages=['misc', 'modules', 'tests', 'dev']
if key in special_packages or 'staticdev' in key:
print('Passing %s package directly' % key)
new_manifest[key]=old_manifest[key]
--
2.11.0
next prev parent reply other threads:[~2018-09-28 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 16:06 [PATCH 1/3] python3: move sqlite files into python-sqlite Ross Burton
2018-09-28 16:06 ` Ross Burton [this message]
2018-09-28 16:06 ` [PATCH 3/3] python: move sqlite module " Ross Burton
2018-09-28 19:30 ` [PATCH 1/3] python3: move sqlite files " Jeroen Hofstee
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=20180928160616.6672-2-ross.burton@intel.com \
--to=ross.burton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox