From: <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: [PATCH 0/1] busybox: add config fragments
Date: Fri, 1 Feb 2013 17:00:21 +0800 [thread overview]
Message-ID: <cover.1359708915.git.Qi.Chen@windriver.com> (raw)
From: Chen Qi <Qi.Chen@windriver.com>
Test Cases
----------
1. Backward Compatibility
Operation:
No config fragments, build busybox
Expected Result:
Everything should be the same with before, especially the .config file
[Actual Result (Success/Fail): Success]
2. Single config fragment: enable a utility
Operation:
Add a config fragment which enables hostid functionality and build core-image-minimal
Expected Result:
hostid command on target could work
[Actual Result (Success/Fail): Success]
3. Multiple config fragments: enable utilities
Followed by test case 2, add a config fragment which enables cal and build minimal image
Expected Result:
cal command on target could work
[Actual Result (Success/Fail): Success]
4. Mutliple config fragments: enable some utilities and disable some utilities
Operation:
Followed by test case 3, add a config fragment which disables and build minimal image
Expected Result:
vi command on target could not work
[Actual Result (Success/Fail): Success]
The following changes since commit 9a26b9c69c47c87ce71a06f76682c187767e7897:
rpm: Ensure native binaries are correctly wrapped (2013-01-30 14:47:30 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/busybox-config-fragments
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/busybox-config-fragments
Chen Qi (1):
busybox: add config fragments
meta/recipes-core/busybox/busybox.inc | 45 +++++++++++++++++++++++++++++++++
1 file changed, 45 insertions(+)
--
1.7.9.5
next reply other threads:[~2013-02-01 9:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 9:00 Qi.Chen [this message]
2013-02-01 9:00 ` [PATCH 1/1] busybox: add config fragments Qi.Chen
2013-02-01 14:18 ` Bruce Ashfield
2013-02-01 18:56 ` Saul Wold
2013-02-01 19:08 ` Bruce Ashfield
2013-02-05 3:01 ` ChenQi
2013-02-05 6:42 ` ChenQi
2013-02-05 16:29 ` Bruce Ashfield
2013-02-12 13:21 ` Richard Purdie
2013-02-12 14:06 ` Bruce Ashfield
2013-02-12 15:32 ` Richard Purdie
2013-02-12 16:50 ` Bruce Ashfield
2013-02-13 16:53 ` Richard Purdie
2013-02-13 16:59 ` Bruce Ashfield
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=cover.1359708915.git.Qi.Chen@windriver.com \
--to=qi.chen@windriver.com \
--cc=Zhenfeng.Zhao@windriver.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