From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH 0/1] Implement ROOTFS postprocess commands
Date: Thu, 28 Mar 2019 13:51:16 +0100 [thread overview]
Message-ID: <d3aea1cd-36c0-a56f-b411-957c2260007b@siemens.com> (raw)
In-Reply-To: <20190326073227.11091-1-claudius.heine.ext@siemens.com>
Hi,
On 26/03/2019 08.32, [ext] claudius.heine.ext@siemens.com wrote:
> From: Claudius Heine <ch@denx.de>
>
> Hi,
>
> this is the first draft of the ROOTFS postprocess implementation.
>
> I switched some of the currently done task over to it as well.
>
> This patchset depends on the 'Clean image pipeline' one, which in turn
> depends on the 'Move isar-image into image class' patchset.
>
> What do you think about this solution?
I am currently working on implementing a preprocessing feature for the
rootfs, e.g. allowing to run commands before any custom packages are
installed and that effected this patch a smidge. So I will first
implement that before sending v2 of this patch.
But since I will be using the same mechanism as shown here, please give
feedback about it.
Thanks,
Claudius
>
> Cheers,
> Claudius
>
> Claudius Heine (1):
> meta/classes/image: implement ROOTFS_POSTPROCESS_COMMAND
>
> meta/classes/image.bbclass | 86 +++++++++++++++++++-------------------
> 1 file changed, 43 insertions(+), 43 deletions(-)
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
prev parent reply other threads:[~2019-03-28 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 7:32 claudius.heine.ext
2019-03-26 7:32 ` [PATCH 1/1] meta/classes/image: implement ROOTFS_POSTPROCESS_COMMAND claudius.heine.ext
2019-03-28 12:51 ` Claudius Heine [this message]
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=d3aea1cd-36c0-a56f-b411-957c2260007b@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=ch@denx.de \
--cc=isar-users@googlegroups.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