public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v3 0/4] Rewrite the image-account-extension in python
Date: Tue, 11 Jul 2023 09:42:31 +0300	[thread overview]
Message-ID: <afa7295180dfca906d7de6a54c4a308f5c14fcc2.camel@ilbers.de> (raw)
In-Reply-To: <20230522065531.2300448-1-tobias.schaffner@siemens.com>

On Mon, 2023-05-22 at 08:55 +0200, T. Schaffner wrote:
> From: Tobias Schaffner <tobias.schaffner@siemens.com>
> 
> This allows us to drop a lot of encoding and parsing code that was
> used
> to transition to shell and therefore makes 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.
> 
> This is a rebased version of the refactoring part of the "allow
> creation
> of users/groups before rootfs creation" patch series to decouple the
> merge of the simplifications.
> 
> Changes since v1:
> - Fix wrong year in copyright of image-account-extension
> 
> Changes since v2:
> - Only set system flag if a new group is created and create a
> unittest
>   that proofs that it is not added for existing groups.
> 
> Tobias Schaffner (4):
>   simplify image-account-extension
>   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                            |   2 +-
>  meta/classes/image-account-extension.bbclass  | 368 ++++++----------
> --
>  testsuite/unittests/README.md                 |  28 ++
>  testsuite/unittests/bitbake.py                |  37 ++
>  testsuite/unittests/rootfs.py                 |  45 +++
>  .../unittests/test_image_account_extension.py | 157 ++++++++
>  6 files changed, 392 insertions(+), 245 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
> 

Applied to next, thanks.

      parent reply	other threads:[~2023-07-11  6:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22  6:55 T. Schaffner
2023-05-22  6:55 ` [PATCH v3 1/4] simplify image-account-extension T. Schaffner
2023-05-22  6:55 ` [PATCH v3 2/4] create a minimal python unittest infrastructure T. Schaffner
2023-05-22  6:55 ` [PATCH v3 3/4] add unittests for the image-account-extension T. Schaffner
2023-05-22  6:55 ` [PATCH v3 4/4] set minimal python version in user_manual to 3.5 T. Schaffner
2023-07-06  4:32 ` [PATCH v3 0/4] Rewrite the image-account-extension in python Uladzimir Bely
2023-07-11  6:42 ` Uladzimir Bely [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=afa7295180dfca906d7de6a54c4a308f5c14fcc2.camel@ilbers.de \
    --to=ubely@ilbers.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