From: Stefan Agner <stefan@agner.ch>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: muhammad_shakeel@mentor.com,
Stefan Agner <stefan.agner@toradex.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] postinsts fixes
Date: Tue, 15 May 2018 18:07:46 +0200 [thread overview]
Message-ID: <e2efa2cc72ff1bf2c9620e1fd9ebaece@agner.ch> (raw)
In-Reply-To: <b80d6b0c-6f27-8c28-26d3-b62019c303c9@linux.intel.com>
On 15.05.2018 17:03, Alexander Kanavin wrote:
> On 05/15/2018 05:04 PM, Stefan Agner wrote:
>> This follows up on the discussion a while ago:
>> https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg104996.html
>
> Took me a moment to realize all three patches are specific to
> opkg/dpkg and do not change how rpm (or general 'postinst handling')
> works. Perhaps you could amend the commit messages to emphasize that?
Patch 1 has opkg in the subject.
Patch 2/3 mention opkg/dpkg in the commit log.
Patch 3 also really edits the DpkgOpkgRootfs class, which should make it
rather obvious.
But I agree for patch 2 it would be good to emphasize it.
How about adding this after the first paragraph:
The behavior for rpm stays the same.
--
Stefan
next prev parent reply other threads:[~2018-05-15 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 14:04 [PATCH 0/3] postinsts fixes Stefan Agner
2018-05-15 14:04 ` [PATCH 1/3] opkg: avoid running postinst scripts twice when using systemd Stefan Agner
2018-06-05 22:17 ` Christopher Larson
2018-05-15 14:04 ` [PATCH 2/3] run-postinsts: Do not rely on /etc/*-postinsts Stefan Agner
2018-05-15 14:04 ` [PATCH 3/3] rootfs.py: Don't install postinsts if package management is present Stefan Agner
2018-05-15 15:03 ` [PATCH 0/3] postinsts fixes Alexander Kanavin
2018-05-15 16:07 ` Stefan Agner [this message]
2018-05-15 16:07 ` Alexander Kanavin
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=e2efa2cc72ff1bf2c9620e1fd9ebaece@agner.ch \
--to=stefan@agner.ch \
--cc=alexander.kanavin@linux.intel.com \
--cc=muhammad_shakeel@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=stefan.agner@toradex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox