public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/9] first wic integration
Date: Wed, 31 Jan 2018 11:12:53 +0100	[thread overview]
Message-ID: <20180131111253.49011346@mmd1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <f302eb9b-9336-c94e-8c04-57809c2c8271@ilbers.de>

Am Wed, 31 Jan 2018 13:02:53 +0300
schrieb Alexander Smirnov <asmirnov@ilbers.de>:

> On 01/31/2018 12:41 PM, Henning Schild wrote:
> > This is the first official post of a series that aims to do two
> > things. 1. integrate wic into Isar so it does not need to be called
> > after bitbake
> > 2. get our copy of wic back to an unmodified version from OE
> > 
> > Many people have been asking for the first, so i think i do not
> > need to motivate that change. Things this series already brings is
> > control over the partition sizes, that we did not have before.
> > The choice in working wks files is still limited. The plugins
> > dealing with bootloaders (isolinux, syslinux etc.) will probably
> > need to be forked (like the efigrub one).
> > 
> > The second one is important so we can update wic in the future and
> > developers do not get confused. Having a fork instead of a copy,
> > without a very good reason, is not a good idea. I found that wic
> > does not need to be changed and plugins can be forked.
> >   
> 
> Are there any changes in user interface? Am I right that old commands 
> still work?

There are no changes. Calling wic manually as non-root does not work
anymore, but that might be unrelated. I think it was broken before. It
is a "du" failing with permission denied, see comment in
scripts/wic_fakeroot. If it did work before, i think it must have been
a hack in the wic-modifications. I also do not fully understand where
the fsck "fail" comes from, wic had modifications there as well.

If the manual non-root call did work before, i will look into that. Or
just change the docs that mention it.

We will need test coverage in CI, but as far as i can tell the whole
wic-side was not covered.

Henning

> Alex
> 
> > Henning
> > 
> > Henning Schild (9):
> >    classes: image: introduce size measuring function, for before
> >      do_*_image
> >    images: new class wic-img for wic intregration
> >    wic: add a bootimg-efi-isar plugin outside the wic tree
> >    Revert "wic: Make the bootimg-efi plugin generate usable images"
> >    Revert "wic: Introduce the `WicExecError` exception class"
> >    Revert "wic: Work around mcopy error"
> >    Revert "wic: Use sudo instead of pseudo"
> >    Revert "wic: Remove sysroot support"
> >    wic: now truly go for the wic version we claim to have
> > 
> >   .../scripts/lib/wic/canned-wks/sdimage-efi.wks     |   2 +-
> >   .../lib/wic/plugins/source/bootimg-efi-isar.py     | 307
> > +++++++++++++++++++++
> > meta/classes/ext4-img.bbclass                      |   7 +-
> > meta/classes/image.bbclass                         |  19 ++
> > meta/classes/wic-img.bbclass                       |  64 +++++
> > scripts/lib/wic/canned-wks/qemux86-directdisk.wks  |   2 +-
> > scripts/lib/wic/engine.py                          |   7 +-
> > scripts/lib/wic/filemap.py                         |   6 +-
> > scripts/lib/wic/help.py                            |   2 -
> > scripts/lib/wic/ksparser.py                        |   4 +-
> > scripts/lib/wic/partition.py                       | 197
> > ++++++++----- scripts/lib/wic/pluginbase.py                      |
> > 11 +- scripts/lib/wic/plugins/imager/direct.py           |  66
> > +++-- scripts/lib/wic/plugins/source/bootimg-efi.py      |  78
> > +----- .../lib/wic/plugins/source/bootimg-partition.py    |   6 +-
> > scripts/lib/wic/plugins/source/bootimg-pcbios.py   |  68 ++---
> > scripts/lib/wic/plugins/source/fsimage.py          |  56
> > ++++ .../lib/wic/plugins/source/isoimage-isohybrid.py   |  28 +-
> > scripts/lib/wic/plugins/source/rawcopy.py          |   2 +-
> > scripts/lib/wic/plugins/source/rootfs.py           |   4 +-
> > scripts/lib/wic/utils/misc.py                      |  33 +--
> > scripts/lib/wic/utils/runner.py                    |  74 ++++-
> > scripts/wic                                        |  27 +-
> > scripts/wic_fakeroot                               |  37 +++ 24
> > files changed, 846 insertions(+), 261 deletions(-) create mode
> > 100644 meta-isar/scripts/lib/wic/plugins/source/bootimg-efi-isar.py
> > create mode 100644 meta/classes/wic-img.bbclass create mode 100644
> > scripts/lib/wic/plugins/source/fsimage.py create mode 100755
> > scripts/wic_fakeroot 
> 


  reply	other threads:[~2018-01-31 10:12 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31  9:41 Henning Schild
2018-01-31  9:41 ` [PATCH 1/9] classes: image: introduce size measuring function, for before do_*_image Henning Schild
2018-01-31  9:41 ` [PATCH 2/9] images: new class wic-img for wic intregration Henning Schild
2018-02-13 14:44   ` Alexander Smirnov
2018-02-13 16:06     ` Henning Schild
2018-01-31  9:41 ` [PATCH 3/9] wic: add a bootimg-efi-isar plugin outside the wic tree Henning Schild
2018-02-12 17:48   ` Jan Kiszka
2018-01-31  9:41 ` [PATCH 4/9] Revert "wic: Make the bootimg-efi plugin generate usable images" Henning Schild
2018-01-31  9:41 ` [PATCH 5/9] Revert "wic: Introduce the `WicExecError` exception class" Henning Schild
2018-01-31  9:41 ` [PATCH 6/9] Revert "wic: Work around mcopy error" Henning Schild
2018-01-31  9:41 ` [PATCH 7/9] Revert "wic: Use sudo instead of pseudo" Henning Schild
2018-01-31  9:41 ` [PATCH 8/9] Revert "wic: Remove sysroot support" Henning Schild
2018-01-31  9:42 ` [PATCH 9/9] wic: now truly go for the wic version we claim to have Henning Schild
2018-01-31 10:11   ` Alexander Smirnov
2018-01-31 10:55     ` Jan Kiszka
2018-01-31 11:11       ` Alexander Smirnov
2018-01-31 11:43         ` Jan Kiszka
2018-01-31 11:53           ` Baurzhan Ismagulov
2018-01-31 12:01             ` Jan Kiszka
2018-01-31 12:28               ` Baurzhan Ismagulov
2018-01-31 13:53                 ` Henning Schild
2018-01-31 14:01                   ` Baurzhan Ismagulov
2018-01-31 14:21                     ` Henning Schild
2018-01-31 10:02 ` [PATCH 0/9] first wic integration Alexander Smirnov
2018-01-31 10:12   ` Henning Schild [this message]
2018-01-31 11:24     ` Baurzhan Ismagulov
2018-01-31 11:47       ` Jan Kiszka
2018-01-31 12:02         ` Baurzhan Ismagulov
2018-01-31 12:15           ` Jan Kiszka
2018-01-31 13:30             ` Jan Kiszka
2018-01-31 13:41               ` Baurzhan Ismagulov
2018-01-31 14:01                 ` Jan Kiszka
2018-01-31 15:21                   ` Baurzhan Ismagulov
2018-01-31 15:46                     ` Henning Schild
2018-01-31 16:13                     ` Jan Kiszka
2018-01-31 13:35             ` Baurzhan Ismagulov
2018-01-31 13:47               ` Henning Schild
2018-01-31 14:00                 ` Baurzhan Ismagulov
2018-01-31 13:46             ` Henning Schild
2018-01-31 13:36           ` Henning Schild
2018-01-31 13:40             ` Baurzhan Ismagulov
2018-01-31 13:05       ` Henning Schild
2018-02-01 12:41 ` [PATCH] images: wic: limit use of sudo and enable manual call again Henning Schild
2018-02-01 12:44   ` Henning Schild
2018-02-01 16:09     ` Baurzhan Ismagulov
2018-02-01 18:10       ` Henning Schild
2018-02-01 18:55         ` Henning Schild
2018-02-12 19:07   ` Henning Schild
2018-02-12 17:27 ` [PATCH 0/9] first wic integration Henning Schild
2018-02-12 18:21   ` Alexander Smirnov
2018-02-12 18:30     ` 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=20180131111253.49011346@mmd1pvb1c.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=asmirnov@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