From: Quentin Schulz <quentin.schulz@cherry.de>
To: rpjday@crashcourse.ca,
YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] ref_manual: add "fragments" and "templates" directories to structure
Date: Wed, 24 Jun 2026 13:01:19 +0200 [thread overview]
Message-ID: <f550e65b-d09b-4890-94f6-7fbc3a932765@cherry.de> (raw)
In-Reply-To: <21c2164f-ac8d-256d-f8ef-c15336fbba3e@crashcourse.ca>
Hi Robert,
On 6/23/26 7:43 PM, Robert P. J. Day via lists.yoctoproject.org wrote:
>
> Add two new entries for the meta/conf/{fragments,templates}
> directories to the structure of OE-Core metadata.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> I didn't bother with the "multiconfig" directory since all it
> contained was an empty default.conf file. So let's just go with these.
>
> diff --git a/documentation/ref-manual/structure.rst b/documentation/ref-manual/structure.rst
> index ff84b250b..96f9c9f34 100644
> --- a/documentation/ref-manual/structure.rst
> +++ b/documentation/ref-manual/structure.rst
> @@ -862,6 +862,25 @@ it is possible to extend that support to other SDK hosts by adding
> additional configuration files in this subdirectory within another
> layer.
>
> +.. _structure-meta-conf-fragments:
> +
> +``meta/conf/fragments/``
> +~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +This directory contains a number of
> +:term:`configuration fragments <Configuration Fragment>` ---
> +top-level build configuration features that can be independently enabled
> +and disabled using standard tooling.
> +
What standard tooling?
> +.. _structure-meta-conf-templates:
> +
> +``meta/conf/templates/``
> +~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +This directory contains default templates to be used as initial files
> +such as ``local.conf``, ``bblayers.conf`` and other files when
> +initializing a new Yocto Project build.
> +
I wouldn't know what makes a template and what they can be used for,
should we point at
documentation/dev-manual/custom-template-configuration-directory.rst for
example?
> .. _structure-meta-files:
>
> ``meta/files/``
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#9843): https://lists.yoctoproject.org/g/docs/message/9843
> Mute This Topic: https://lists.yoctoproject.org/mt/119945115/6293953
> Group Owner: docs+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/docs/unsub [quentin.schulz@cherry.de]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2026-06-24 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 17:43 [PATCH] ref_manual: add "fragments" and "templates" directories to structure Robert P. J. Day
2026-06-24 11:01 ` Quentin Schulz [this message]
2026-06-24 17:50 ` [docs] " Robert P. J. Day
2026-06-25 8:23 ` Antonin Godard
2026-07-02 7:37 ` Antonin Godard
2026-07-02 8:40 ` Robert P. J. Day
2026-07-02 11:53 ` Antonin Godard
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=f550e65b-d09b-4890-94f6-7fbc3a932765@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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