From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [RFC PATCH 0/1] Image minimization
Date: Wed, 29 May 2019 12:45:05 +0200 [thread overview]
Message-ID: <20190529104506.10508-1-claudius.heine.ext@siemens.com> (raw)
From: Claudius Heine <ch@denx.de>
Hi,
here is a RFC patch that adds a minimization extensions to images.
The basic idea behind this is that it allows to remove specific packages and
files from the root file system in a post-processing step. This is useful in
case there are tight storage space restrictions. It breaks the package
management in multiple different ways and degrees, but the main idea is to
reduce the root file system to a minimal set of files that are necessary for the
device to still perform its function.
I envision the `IMAGE_MINIMIZATION_FEATURES`, `IMAGE_MINIMIZATION_PACKAGES` and
`IMAGE_MINIMIZATION_FILES` to be the user facing interface for this.
While removing packages, I use the dpkg from the buildchroot in order to be
independent from the tools on the image. This also allows to remove dpkg while
still being able to use it.
I would like to hear some input about the general design, before I start
cleaning that up and testing it more intensively.
thanks,
Claudius
Claudius Heine (1):
add minimization image extension
.../recipes-core/images/isar-image-ubi.bb | 2 +
.../image-minimizing-extension.bbclass | 80 +++++++++++++++++++
meta/classes/image.bbclass | 1 +
meta/classes/rootfs.bbclass | 3 +-
4 files changed, 85 insertions(+), 1 deletion(-)
create mode 100644 meta/classes/image-minimizing-extension.bbclass
--
2.20.1
next reply other threads:[~2019-05-29 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 10:45 claudius.heine.ext [this message]
2019-05-29 10:45 ` [RFC PATCH 1/1] add minimization image extension claudius.heine.ext
2019-05-29 11:22 ` Henning Schild
2019-05-29 11:28 ` Henning Schild
2019-05-29 11:29 ` Jan Kiszka
2019-05-29 10:56 ` [RFC PATCH 0/1] Image minimization Jan Kiszka
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=20190529104506.10508-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