Re: [PATCH] images: wic: limit use of sudo and enable manual call again

[Baurzhan Ismagulov <ibr@radix50.net>]

On Thu, Feb 01, 2018 at 01:44:59PM +0100, Henning Schild wrote:
> This patch addresses the two main issues found in the reviews. The big
> "sudo" and the broken "call it manually". The latter one is not fully
> solved because users will have to call "isar-wic" instead of "wic".
> 
> I would even suggest to not fold this into the series and apply it on
> top. It kind of shows some of the hacks required to wrap an unmodified
> wic. The patch cleanly applies on top of the series i posted so far.

Wow, that's an interesting approach, thanks for the effort. Splitting wic and
isar-wic reduces user surprise, which would be a good thing. Do I understand
correctly, you replace du and mkfs.* with your own versions and execute the
respective command with superuser privileges? Let me read the code in more
detail, but if yes, I'm not sure the complexity is worth the use case.

I haven't finished reading the first series yet. Some background questions:

1. Are there any disadvantages of using wic, compared to the old-school
   ext4-img?

2. AFAICT, Yocto still maintains both wic and image-types.bbclass. Why don't
   they move to wic completely?

3. With wic-img.bbclass, how does one choose fs type? E.g., quickly generate
   the same image on ext4 and ext3.

4. How to add a new fs type to wic?

I see that you add wic-img.bbclass, but no image uses it. Would it be useful to
migrate all images to wic, remove ext4-img, and remove wic usage from the docs?
If that solution would be "clean" and we have answers to the questions above, I
could possibly live with all-in sudo, although I'd still prefer keeping the
sudo hack for a while.

With kind regards,
Baurzhan.