Closed zuka0828 closed 5 years ago
Nope, this is not supported. The idea is so far to express artifacts contributing to the final local.conf via local_conf_header sections in the different kas files you may include per layer.
PS: we prefer to discuss on the mailing list.
@jan-kiszka Thanks, I'd like to close the issue. It might be useful if kas supports loading existing local.conf(.sample)
which would be provided in extension layers.
PS: we prefer to discuss on the mailing list.
OK, I will from the next time.
kas generates the
local.conf
andbblayers.conf
in the build directory from the headers (local_conf_header
andbblayers_conf_header
) and other kas variables (machine
,distro
, and the layers inrepos
).Is it possible to use the existing template configs in each layer with kas? i.e.
meta-xxx/conf/local.conf.sample
andmeta-xxx/conf/local.conf.sample
, that are copied byoe-init-build-env
if we setTEMPLATECONF=meta-xxx/conf
I cannot find any information how to do this indocs/userguide.rst
.