From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Fix for #9636: wic script should use argparse instead of optparse
Date: Tue, 2 May 2017 17:38:17 +0300 [thread overview]
Message-ID: <cover.1493735327.git.ed.bartosh@linux.intel.com> (raw)
Hi,
This patchset contains two patches from Andreas J. Reichel's patchset and
a fix for wic test case.
Description taken from the original patchset:
wic uses optparse and a rather complicated approach of its initialization.
It is much easier to switch from the deprecated optparse to the argparse library,
which also supports sub-commands, which wic heavily makes use of.
The following changes since commit 381897c64069ea43d595380a3ae913bcc79cf7e1:
build-appliance-image: Update to master head revision (2017-05-01 08:56:47 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ed/wic/wip
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/wic/wip
Andreas J. Reichel (2):
wic: Use argparse instead of optparse
wic: Add missing text to usage and help strings
Ed Bartosh (1):
selftest: fix test_unsupported_subcommand test case
meta/lib/oeqa/selftest/wic.py | 3 +-
scripts/lib/wic/engine.py | 11 ++-
scripts/lib/wic/help.py | 25 +++--
scripts/wic | 213 ++++++++++++++++++++++++++----------------
4 files changed, 156 insertions(+), 96 deletions(-)
--
Regards,
Ed
next reply other threads:[~2017-05-02 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 14:38 Ed Bartosh [this message]
2017-05-02 14:38 ` [PATCH 1/3] wic: Use argparse instead of optparse Ed Bartosh
2017-05-02 14:38 ` [PATCH 2/3] wic: Add missing text to usage and help strings Ed Bartosh
2017-05-02 14:38 ` [PATCH 3/3] selftest: fix test_unsupported_subcommand test case Ed Bartosh
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.1493735327.git.ed.bartosh@linux.intel.com \
--to=ed.bartosh@linux.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 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.