No way do edit templateconf.cfg?

[Schlumpf]

Is there any way to create a custom build/conf/templateconf.cfg with kas?

[tprrt]

Hi,

I just wanted to ask the same question because I would like to use the local.conf.sample, bblayer.conf.sample from my custom layer, in order to be able to use the same sample files to create the basic configuration, whether it is with or without kas.

Does anyone know if there is a way to do it?

Best regards,
Thomas

[jan-kiszka]

What would be the desired workflow? I'm asking because a kas configuration consists more than the content of local.conf and bblayer.conf in the end, and that delta would still require user input before you could build anything.

[tprrt]

Hi @jan-kiszka,

The target was to use sample files (local.conf.sample, bblayers.conf.sample, conf-notes.txt...) provided by one of layers fetched, to create local.conf, bblayer.conf.

A layer can be used in many way, especially without kas (git-repo, combo layer...). And currently to validate these sample files it is required to copy the content into the kas yaml in order to validate them.

Best regards,
Thomas

[jan-kiszka]

Well, "sample" is an example while kas is about describing the final thing, normally.

But maybe we could extend keys you can add to local_conf_header and bblayer_conf_header with a file inclusion mechanism (as an alternative to strings). Would require something similar to specifying layer patches (repo, path). Would that help already?

[henning-schild]

One could add a kas.yml.sample where a layer would keep its example written in kas lingo. On top we could have kas to-bitbake kas.yml.sample local.conf.sample. That way a layer maintainer would maintain the kas.yml.sample and have the bitbake sample generated for non-kas users.

[jan-kiszka]

If the kas sample files would have widely the same content as the corresponding conf sample files, that would not be optimal, even if one is generated out of the other.

[jan-kiszka]

Any new insights on this topic meanwhile?

[fschrempf]

The content of local.conf.sample and bblayers.conf.sample can be covered by kas configuration which is good enough for me, even if that means having redundant sample files in case non-kas use cases should be supported.

The thing I miss in kas is a way to select the path for conf-notes.txt or is there one and I missed it?

[jan-kiszka]

Is conf-notes.txt related to this topic? I find very little traces in OE core and zero documentation on it. If it is unrelated to templateconf.cfg, please open a separate issue. In any case, I would need some education on how it is used.

[fschrempf]

It's related to templateconf.cfg as the path specified there is also used for specifying a custom conf-notes.txt. But maybe I can just pass a value for TEMPLATECONF through the environment. I need to try this. Anyway it would be more like something nice-to-have.

There's a bit of documentation:

• https://docs.yoctoproject.org/ref-manual/variables.html?highlight=templateconf#term-TEMPLATECONF
• https://docs.yoctoproject.org/dev-manual/common-tasks.html#creating-a-custom-template-configuration-directory

[whni]

@fschrempf Hi I also have the same question. For the TEMPLATECONF env, it will be overwritten by https://github.com/openembedded/openembedded-core/blob/kirkstone/scripts/oe-setup-builddir#L41