From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: Zhihang Wei <wzh@ilbers.de>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/6] Model isar-exclude-docs as rootfs feature
Date: Fri, 2 Oct 2026 08:06:45 +0000 [thread overview]
Message-ID: <b45767ee31c71c8d8dd31e58914430d48a9cdecc.camel@siemens.com> (raw)
In-Reply-To: <20260924073811.4058349-1-felix.moessbauer@siemens.com>
On Thu, 2026-09-24 at 09:38 +0200, Felix Moessbauer wrote:
> The isar-exclude-docs package provides mechanisms to exclude
> documentation from the image. Technically this is implemented
> by a dpkg filter, as well as a postinst script to strip the
> documentation installed prior to installing the isar-exclude-docs
> package.
Hi,
is there anything missing from my side to get this merged?
I would like to send out the remainder of the build-time improvement
series by today (which depends on this). Then we have all the code
available my talk "Isar build time reduction" on the isar community
event is covering.
Best regards,
Felix
>
> This has the major drawback of first installing the documentation
> (as isar-exclude-docs is installed along with ROOTFS_PACKAGES) and
> then removing it again - which is even an emulated task and by that
> super slow on a larger rootfs. Further, it does not handle cases
> where docs are generated in a postinst script.
>
> We now change this to configure apt prior to installing packages.
> This results in less being installed into the rootfs. After that,
> a final cleanup path from outside the chroot strip the remaining bits.
>
> Best regards,
> Felix Moessbauer
>
> Felix Moessbauer (6):
> rootfs: add feature to clean isar generated dpkg config
> image: add IMAGE_ROOTFS_FEATURES to set rootfs features of the image
> isar-exclude-docs: model via rootfs feature
> rootfs: also purge package changelogs on exclude-docs
> kas: port isar-exclude-docs to rootfs feature
> testsuite: replace isar-exclude-docs by rootfs feature
>
> RECIPE-API-CHANGELOG.md | 14 ++++++
> kas/opt/Kconfig | 9 ++++
> .../exclude-docs.yaml} | 4 +-
> kas/package/Kconfig | 11 -----
> meta-isar/conf/local.conf.sample | 6 ++-
> .../recipes-core/images/isar-image-ci.bb | 2 +
> .../recipes-core/images/isar-rootfs-ci.bb | 1 +
> meta/classes-recipe/image.bbclass | 3 ++
> meta/classes-recipe/rootfs.bbclass | 45 +++++++++++++++++++
> .../isar-exclude-docs_0.2.3.bb | 4 ++
> scripts/generate_yaml.sh | 1 -
> testsuite/cibuilder.py | 1 -
> 12 files changed, 85 insertions(+), 16 deletions(-)
> rename kas/{package/pkg_isar-exclude-docs.yaml => opt/exclude-docs.yaml} (58%)
>
> --
> 2.55.0
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/b45767ee31c71c8d8dd31e58914430d48a9cdecc.camel%40siemens.com.
next prev parent reply other threads:[~2026-10-02 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 7:38 'Felix Moessbauer' via isar-users
2026-09-24 7:38 ` [PATCH 1/6] rootfs: add feature to clean isar generated dpkg config 'Felix Moessbauer' via isar-users
2026-09-24 7:38 ` [PATCH 2/6] image: add IMAGE_ROOTFS_FEATURES to set rootfs features of the image 'Felix Moessbauer' via isar-users
2026-09-24 7:38 ` [PATCH 3/6] isar-exclude-docs: model via rootfs feature 'Felix Moessbauer' via isar-users
2026-09-24 7:38 ` [PATCH 4/6] rootfs: also purge package changelogs on exclude-docs 'Felix Moessbauer' via isar-users
2026-09-24 7:38 ` [PATCH 5/6] kas: port isar-exclude-docs to rootfs feature 'Felix Moessbauer' via isar-users
2026-09-24 7:38 ` [PATCH 6/6] testsuite: replace isar-exclude-docs by " 'Felix Moessbauer' via isar-users
2026-10-02 8:06 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-10-02 8:12 ` [PATCH 0/6] Model isar-exclude-docs as " Zhihang Wei
2026-10-02 10:03 ` 'MOESSBAUER, Felix' via isar-users
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=b45767ee31c71c8d8dd31e58914430d48a9cdecc.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=wzh@ilbers.de \
/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