public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Paul Barker <paul@pbarker.dev>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v5 04/10] wic: provide oe-core wks files
Date: Tue, 24 Feb 2026 12:38:30 -0500	[thread overview]
Message-ID: <aZ3iFjn1BpA_6eo4@localhost.localdomain> (raw)
In-Reply-To: <afa3b3fb5c285e9d0a2b55a753244df88ac70465.camel@pbarker.dev>

On Tue 2026-02-24 @ 10:08:30 AM, Paul Barker wrote:
> On Mon, 2026-02-23 at 16:50 -0500, Trevor Woerner via
> lists.openembedded.org wrote:
> > By convention, wic will look for a "wic" directory in the top-level
> > of all BBLAYERS in order to find *wks files. oe-core was the only
> > exception; it stored its *wks files in scripts/lib/wic/canned-wks.
> > Take the *wks, *wks.in, *inc, and *cfg files that were in the old wks
> > location and place them in a "wic" top-level directory in the oe-core
> > layer, thereby following the convention of every other layer.
> > 
> > Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> > ---
> > changes in v5
> > - rebase with master
> > - split patchset out again
> > 
> > v4: skipped to align/combine with other patch set
> > 
> > changes in v3:
> > - squashed into 1 large patch
> > 
> > changes in v2:
> > - none
> > ---
> >  meta/classes-recipe/image_types_wic.bbclass |  2 +-
> >  meta/wic/common.wks.inc                     |  3 +++
> >  meta/wic/directdisk-bootloader-config.cfg   | 27 +++++++++++++++++++++
> >  meta/wic/directdisk-bootloader-config.wks   |  8 ++++++
> >  meta/wic/directdisk-gpt.wks                 | 10 ++++++++
> >  meta/wic/directdisk-multi-rootfs.wks        | 23 ++++++++++++++++++
> >  meta/wic/directdisk.wks                     |  8 ++++++
> >  meta/wic/efi-bootdisk.wks.in                |  3 +++
> >  meta/wic/efi-uki-bootdisk.wks.in            |  3 +++
> >  meta/wic/mkdisk-ufs.wks                     |  5 ++++
> >  meta/wic/mkefidisk.wks                      | 11 +++++++++
> >  meta/wic/mkhybridiso.wks                    |  7 ++++++
> >  meta/wic/qemuloongarch.wks                  |  3 +++
> >  meta/wic/qemuriscv.wks                      |  3 +++
> >  meta/wic/qemux86-directdisk.wks             |  8 ++++++
> >  meta/wic/sdimage-bootpart.wks               |  6 +++++
> >  meta/wic/systemd-bootdisk.wks               | 11 +++++++++
> >  17 files changed, 140 insertions(+), 1 deletion(-)
> >  create mode 100644 meta/wic/common.wks.inc
> >  create mode 100644 meta/wic/directdisk-bootloader-config.cfg
> >  create mode 100644 meta/wic/directdisk-bootloader-config.wks
> >  create mode 100644 meta/wic/directdisk-gpt.wks
> >  create mode 100644 meta/wic/directdisk-multi-rootfs.wks
> >  create mode 100644 meta/wic/directdisk.wks
> >  create mode 100644 meta/wic/efi-bootdisk.wks.in
> >  create mode 100644 meta/wic/efi-uki-bootdisk.wks.in
> >  create mode 100644 meta/wic/mkdisk-ufs.wks
> >  create mode 100644 meta/wic/mkefidisk.wks
> >  create mode 100644 meta/wic/mkhybridiso.wks
> >  create mode 100644 meta/wic/qemuloongarch.wks
> >  create mode 100644 meta/wic/qemuriscv.wks
> >  create mode 100644 meta/wic/qemux86-directdisk.wks
> >  create mode 100644 meta/wic/sdimage-bootpart.wks
> >  create mode 100644 meta/wic/systemd-bootdisk.wks
> 
> Can we move these files from scripts/lib/wic/canned-wks to the new
> location before removing wic, i.e. re-order this and the previous
> commit? That would better preserve the history of these files and
> simplify the diff.

Great idea! I'm disappointed I didn't think of it :-)


  reply	other threads:[~2026-02-24 17:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 21:49 [PATCH v5 00/10] standalone wic Trevor Woerner
2026-02-23 21:49 ` [PATCH v5 01/10] wic: re-implement sector-size support Trevor Woerner
2026-02-24  9:52   ` [OE-core] " Paul Barker
2026-02-24 18:40     ` Trevor Woerner
2026-02-24 21:35       ` Paul Barker
2026-02-23 21:50 ` [PATCH v5 02/10] ufs image class: add Trevor Woerner
2026-02-24 10:02   ` [OE-core] " Paul Barker
2026-02-24 10:15     ` Paul Barker
2026-02-24 17:56     ` Trevor Woerner
2026-02-24 21:17       ` Paul Barker
2026-02-25  0:38         ` Trevor Woerner
2026-02-23 21:50 ` [PATCH v5 03/10] wic: remove Trevor Woerner
2026-02-24 10:05   ` [OE-core] " Paul Barker
2026-02-24 17:37     ` Trevor Woerner
2026-02-23 21:50 ` [PATCH v5 04/10] wic: provide oe-core wks files Trevor Woerner
2026-02-24 10:08   ` [OE-core] " Paul Barker
2026-02-24 17:38     ` Trevor Woerner [this message]
2026-02-23 21:50 ` [PATCH v5 05/10] wic: add recipe Trevor Woerner
2026-02-23 21:50 ` [PATCH v5 06/10] oe-selftest/cases/wic.py: update WicTestCase Trevor Woerner
2026-02-23 21:50 ` [PATCH v5 07/10] oe-selftest/cases/wic.py: oe-selftest -r wic.CLITests -> PASS Trevor Woerner
2026-02-23 21:50 ` [PATCH v5 08/10] oe-selftest/cases/wic.py: oe-selftest -r wic.ModifyTests " Trevor Woerner
2026-02-23 21:50 ` [PATCH v5 09/10] oe-selftest/cases/wic.py: oe-selftest -r wic.Wic " Trevor Woerner
2026-02-23 21:50 ` [PATCH v5 10/10] oe-selftest/cases/wic.py: oe-selftest -r wic.Wic2 " Trevor Woerner

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=aZ3iFjn1BpA_6eo4@localhost.localdomain \
    --to=twoerner@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    /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