Re: [OE-core] [PATCH v6 0/9] standalone wic

["Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>]

On Wed Feb 25, 2026 at 8:49 AM CET, Trevor Woerner via lists.openembedded.org wrote:
> This series of patches splits wic out from oe-core into its own 
> standalone utility. The wic utility will continue to be under The Yocto
> Project umbrella, but will no longer be integrated into the project
> as part of oe-core. The ultimate goal is to make wic a completely
> independent tool, hosted on PyPI, with its own tests, development
> roadmap, and releases.
>
> Some benefits include:
> - relieving the oe-core maintainers from having to review wic patches
> - allow the tool to be used outside of The Yocto Project
> - provide more flexibility to explore other features, libraries,
>   mechanisms, etc 
>
> These changes have been tested with oe-selftest as follows:
>         $ sudo .../layers/openembedded-core/scripts/runqemu-gen-tapdevs <my numeric group id> 4
>         $ oe-selftest -v -r wic 
>
> Previously, I had two separate patch sets for wic on oe-core: one 
> to create a standalone utility, and one to re-implement variable
> sector-size handling. Both these were combined to create a combined "v5"
> patch set.
>
> In v6 the major changes are:
> - code cleanups to remove cases of "if sector_size and sector_size =
>   512" in places where we can guarantee sector_size will exist
> - cleanups to replace "getattr(var, 'sector_size', 512) or 512" since
>   the 3rd arg to getattr() is already setting a default if the variable
>   name is not found
> - many comment and commit comment improvements
> - error out if extraopts includes options to set the sector-size in wks
>   files
> - patch 2 (add ufs class) was dropped
> - patches 3 and 4 were reversed (move/save wks files before removing the
>   rest of wic from oe-core)
>
> For the patch sets up to and including v5:
> For the standalone patch set:
> v1: an RFC patchset was sent out, split up into small patches for easy
>     review
> v2: add wic utility to list of native dependencies of
>     image_types_wic.bbclass
> v3: squash all commits together to apply atomically
> v4: (does not exist)
> v5: rebase on latest master
>     split commits back out acknowledging any bisection that lands
>     between them will fail
>     combine with sector-size patch
>
> For the sector-size patch:
> v1: initial patch set 
> v2: add Mark as co-author of ufs class
>     try to fix a build warning when not using wic 
> v3: actually fix warning when not using wic 
> v4: deprecate, but allow, WIC_SECTOR_SIZE to continue to be used to set 
>     the sector-size both from config files and the environment
>     warn when both are used, but prefer cmdline value
>     change partition type of sample wks to gpt 
> v5: fix a bug where WIC_SECTOR_SIZE is not given anywhere
>     combine with standalone patch set 
>
>
> Trevor Woerner (9):

Hi Trevor,

Thanks for the new version.

We have some test failure as the wic tool is not found in path. I
believe we already discussed that previously, but I'm not sure what was
the conclusion.

Poky - The Yocto Project testing distribution
Running '. ./init-build-env; wic create directdisk -e core-image-sato -o ${BUILDDIR}/tmp/deploy/wic_images/qemux86/directdisk/core-image-sato/' with output to /srv/pokybuild/yocto-worker/wic/build/build/command-1-cmds.log in /srv/pokybuild/yocto-worker/wic/build/build
/bin/bash: line 1: wic: command not found

https://autobuilder.yoctoproject.org/valkyrie/#/builders/15/builds/3190

I will let other tests finish, so we can have an overview of the
situation.

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com