From: <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: qingtao.cao@windriver.com
Subject: [PATCH V4 0/4] Postinst logging reimplementation
Date: Thu, 23 May 2013 12:43:32 +0800 [thread overview]
Message-ID: <cover.1369284008.git.Qi.Chen@windriver.com> (raw)
From: Chen Qi <Qi.Chen@windriver.com>
Goal:
1. Enable postinst logging if 'debug-tweaks' is in IMAGE_FEATURES
2. Make rpm, opkg and dpkg not depend on IMAGE_FEATURES and POSTLOG
Implementation:
1. The run-postinst scripts will log outputs by checking the configuration in ${sysconfdir}/default/postinst.
2. The log location is by default ${localstatedir}/log/postinstall.log.
But it could be configured to a different location.
The following changes since commit 21089515bd18ba18e86ec8f72ff8141b9fb1dea8:
ref-manual: Added xmlto and dblatex packages for docs (2013-05-22 17:23:41 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/postinst-logging-reimplementation
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/postinst-logging-reimplementation
Chen Qi (4):
image.bbclass: add postinst_enable_logging
dpkg: modify the run-postinst script to enable postinst logging
opkg: modify the run-postinst script to enable postinst logging
rpm-postinsts.bb: enable postinst logging
meta/classes/image.bbclass | 11 +++++++++++
meta/recipes-devtools/dpkg/dpkg.inc | 11 ++++++-----
meta/recipes-devtools/opkg/opkg.inc | 7 ++++++-
meta/recipes-devtools/rpm/rpm-postinsts.bb | 17 +++++++++--------
4 files changed, 32 insertions(+), 14 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-05-23 4:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 4:43 Qi.Chen [this message]
2013-05-23 4:43 ` [PATCH V4 1/4] image.bbclass: add postinst_enable_logging Qi.Chen
2013-05-23 4:43 ` [PATCH V4 2/4] dpkg: modify the run-postinst script to enable postinst logging Qi.Chen
2013-05-23 4:43 ` [PATCH V4 3/4] opkg: " Qi.Chen
2013-05-23 4:43 ` [PATCH V4 4/4] rpm-postinsts.bb: " Qi.Chen
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.1369284008.git.Qi.Chen@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=qingtao.cao@windriver.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.