public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "T. Schaffner" <tobias.schaffner@siemens.com>
To: <isar-users@googlegroups.com>
Cc: <quirin.gylstorff@siemens.com>, <michael.adler@siemens.com>,
	"Tobias Schaffner" <tobias.schaffner@siemens.com>
Subject: [PATCH 0/5] allow creation of users/groups before rootfs creation
Date: Wed, 25 Jan 2023 10:01:51 +0100	[thread overview]
Message-ID: <20230125090156.284309-1-tobias.schaffner@siemens.com> (raw)

From: Tobias Schaffner <tobias.schaffner@siemens.com>

This patch series will allow to specify a `pre` flag for the USER_ and
GROUP_ bitbake variables. If this flag is set to `true` the given user
or group will be created in the rootfs configuration step instead of on
rootfs postprocessing. This is helpful when a specific id should be used
which would otherwise be picked by a user or group created by one of the
installed packages.

A rewrite of the image-account-extension in python was done on the way.
This allows us to drop a lot of encoding and parsing code that was used
to transition to shell and therefore made it easier to read and maintain.

Using python functions for more complex tasks allows us the usage of
unittests. A very basic infrastructure for unittesting using the build
in python unittest and the bb.parse module was added. This was used to
test the re-implementation of the image-account-extension as a first
showcase.

Tobias Schaffner (5):
  simplify image-account-extension
  allow creation of users/groups before rootfs creation
  create a minimal python unittest infrastructure
  add unittests for the image-account-extension
  set minimal python version in user_manual to 3.5

 doc/user_manual.md                            |   4 +-
 meta/classes/image-account-extension.bbclass  | 391 +++++++-----------
 testsuite/unittests/README.md                 |  28 ++
 testsuite/unittests/bitbake.py                |  37 ++
 testsuite/unittests/rootfs.py                 |  45 ++
 .../unittests/test_image_account_extension.py | 175 ++++++++
 6 files changed, 434 insertions(+), 246 deletions(-)
 create mode 100644 testsuite/unittests/README.md
 create mode 100644 testsuite/unittests/bitbake.py
 create mode 100644 testsuite/unittests/rootfs.py
 create mode 100644 testsuite/unittests/test_image_account_extension.py

-- 
2.34.1


             reply	other threads:[~2023-01-25  9:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25  9:01 T. Schaffner [this message]
2023-01-25  9:01 ` [PATCH 1/5] simplify image-account-extension T. Schaffner
2023-01-25  9:01 ` [PATCH 2/5] allow creation of users/groups before rootfs creation T. Schaffner
2023-01-25  9:01 ` [PATCH 3/5] create a minimal python unittest infrastructure T. Schaffner
2023-01-25  9:01 ` [PATCH 4/5] add unittests for the image-account-extension T. Schaffner
2023-01-25  9:01 ` [PATCH 5/5] set minimal python version in user_manual to 3.5 T. Schaffner
2023-01-25 13:29 ` [PATCH 0/5] allow creation of users/groups before rootfs creation Henning Schild
2023-01-25 13:44   ` Gylstorff Quirin
2023-01-25 16:29     ` Henning Schild
2023-01-25 20:55       ` Schaffner, Tobias
2023-01-25 21:38         ` Henning Schild
2023-01-26  8:21           ` Schaffner, Tobias
2023-01-26  8:48             ` Florian Bezdeka
2023-01-26 10:27               ` Henning Schild
2023-01-26  9:59             ` Henning Schild

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=20230125090156.284309-1-tobias.schaffner@siemens.com \
    --to=tobias.schaffner@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=michael.adler@siemens.com \
    --cc=quirin.gylstorff@siemens.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