From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [PATCH 0/1] Move isar-image into image class
Date: Wed, 20 Mar 2019 16:55:23 +0100 [thread overview]
Message-ID: <20190320155524.17713-1-claudius.heine.ext@siemens.com> (raw)
From: Claudius Heine <ch@denx.de>
Hi,
this patch moves the isar-image into the image class as a first
preparation for further refactoring done to the image creation pipeline.
The following steps will be:
- Implementation of a clean image generation pipeline, as described in
github issue #46, no functional change intended
- Implementation of a rootfs postprocessing functionality similar to
how OE solved it
- Splitting up of the isar-bootstrap-helper/setup_root_file_system
function to allow adding tasks/function that are executed between
copying of isar-bootstrap and installation of custom packages etc.
-> rootfs preprocessing
- Moving existing functionality into idempotent tasks/functions and
into the correct position within the pipeline
- Implementing additional post/pre-process tasks (user management,
rootfs minimization, debug settings, etc.)
- Deprecating transient packages if no other uses for this can be
found.
regards,
Claudius
Claudius Heine (1):
meta: merges isar-image into image class
meta/classes/image.bbclass | 86 +++++++++++++++++++++++++++++--
meta/classes/isar-image.bbclass | 90 +--------------------------------
2 files changed, 85 insertions(+), 91 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-20 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 15:55 claudius.heine.ext [this message]
2019-03-20 15:55 ` [PATCH 1/1] meta: merges " claudius.heine.ext
2019-03-20 16:50 ` Jan Kiszka
2019-03-21 7:24 ` Claudius Heine
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=20190320155524.17713-1-claudius.heine.ext@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