From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] best practices regarding using WKS_FILES to reference multiple .wks files?
Date: Mon, 4 Oct 2021 05:34:14 -0400 (EDT) [thread overview]
Message-ID: <8b867c34-b494-be37-736e-cc1ed3aa0ec@crashcourse.ca> (raw)
In-Reply-To: <20211004082421.2rgtcfjxodmkrq5e@fedora>
On Mon, 4 Oct 2021, Quentin Schulz wrote:
> Hi Robert,
>
> On Sun, Oct 03, 2021 at 10:53:54AM -0400, Robert P. J. Day wrote:
> >
> > quick observation -- variable glossary makes no reference to
> > WKS_FILES variable (or a few other wic-related variables as i think i
> > mentioned once, but that's not why we're here).
> >
> > simple practice for wic is to define a single .wks file which
> > defines all partitioning for the target. however, what i'm running
> > into in my current project is that that single .wks file defines a
> > couple dozen partitions, many of which are maintained by a number of
> > different developers.
> >
> > unsurprisingly, since all this content is in a single file, and
> > those developers are regularly tweaking their partition attributes,
> > it's a regular occurrence to have commits step on each other when
> > merging to master.
> >
> > is it reasonable (or even doable) to define a collection of
> > reasonably independent .wks files that, collectively, define the final
> > partitioning, and use WKS_FILES to pull them all in, thus avoiding all
> > those merge conflicts?
> >
>
> No. WKS_FILES is not doing what you think it is.
story of my life. :-)
> WKS_FILES is a list of candidates for the .wks file that will be used by
> wic. First to be found (left to right) will be used.
> c.f. https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/image_types_wic.bbclass#n57,
> https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/image_types_wic.bbclass#n39
>
> What I found reading the code is that an include statement should work
> in the wks file, c.f. https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/lib/wic/ksparser.py#n282
>
> I don't know if they are supposed to be in the same directory, if
> the path after the include directive is absolute, relative and if
> relative, to which directory.
>
> If that works, I think this is something that should be documented
> :)
yup, that could very well be what i'm after, having the same effect.
rday
next prev parent reply other threads:[~2021-10-04 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 14:53 best practices regarding using WKS_FILES to reference multiple .wks files? Robert P. J. Day
2021-10-04 8:24 ` [docs] " Quentin Schulz
2021-10-04 9:34 ` Robert P. J. Day [this message]
2021-10-05 17:22 ` Michael Opdenacker
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=8b867c34-b494-be37-736e-cc1ed3aa0ec@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@theobroma-systems.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;
as well as URLs for NNTP newsgroup(s).