From: Otavio Salvador <otavio@ossystems.com.br>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/5] Postinst trigger improvements for images
Date: Tue, 6 Mar 2012 17:24:10 +0000 [thread overview]
Message-ID: <cover.1331054558.git.otavio@ossystems.com.br> (raw)
This patchset make consistent and more meanful the name used as
postinst trigger in rootfs.
The following changes since commit d7b8c247227f3cc82f92292407f548927e9fde78:
base.bbclass: Fix PACKAGECONFIG handling when no flags are set (2012-03-05 13:03:41 -0800)
are available in the git repository at:
git://github.com/OSSystems/oe-core master
https://github.com/OSSystems/oe-core/tree/HEAD
Otavio Salvador (5):
run-postinsts: fix opkg data path
image.bbclass: fix rootfs generation without package management tools
rootfs_rpm.bbclass: rename postinst trigger script
opkg: rename postinst trigger script
dpkg: rename postinst trigger script
meta/classes/core-image.bbclass | 2 --
meta/classes/image.bbclass | 7 +++++--
meta/classes/rootfs_rpm.bbclass | 6 +++---
meta/recipes-devtools/dpkg/dpkg.inc | 8 ++++----
.../dpkg/run-postinsts/run-postinsts | 4 ++--
.../dpkg/run-postinsts/run-postinsts.awk | 2 +-
meta/recipes-devtools/dpkg/run-postinsts_1.0.bb | 2 +-
meta/recipes-devtools/opkg/opkg.inc | 8 ++++----
8 files changed, 20 insertions(+), 19 deletions(-)
--
1.7.2.5
next reply other threads:[~2012-03-06 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 17:24 Otavio Salvador [this message]
2012-03-06 17:24 ` [PATCH v2 1/5] run-postinsts: fix opkg data path Otavio Salvador
2012-03-06 17:24 ` [PATCH v2 2/5] image.bbclass: fix rootfs generation without package management tools Otavio Salvador
2012-03-06 17:24 ` [PATCH v2 3/5] rootfs_rpm.bbclass: rename postinst trigger script Otavio Salvador
2012-03-06 17:24 ` [PATCH v2 4/5] opkg: " Otavio Salvador
2012-03-06 17:24 ` [PATCH v2 5/5] dpkg: " Otavio Salvador
2012-03-13 16:02 ` [PATCH v2 0/5] Postinst trigger improvements for images Saul Wold
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.1331054558.git.otavio@ossystems.com.br \
--to=otavio@ossystems.com.br \
--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