RE: [OE-core] [PATCH 1/2] scripts/oe-setup-builddir: copy site.conf.sample out of template directories (if it exists)

[Peter Kjellerstedt <peter.kjellerstedt@axis.com>]

> -----Original Message-----
> From: Alexander Kanavin <alex.kanavin@gmail.com>
> Sent: den 7 juli 2022 16:48
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: openembedded-core@lists.openembedded.org; Alexander Kanavin
> <alex@linutronix.de>
> Subject: Re: [OE-core] [PATCH 1/2] scripts/oe-setup-builddir: copy
> site.conf.sample out of template directories (if it exists)
> 
> On Thu, 7 Jul 2022 at 16:38, Peter Kjellerstedt
> <peter.kjellerstedt@axis.com> wrote:
> 
> > And in case you wonder what that wrapper actually does, it creates the
> > bblayers.conf.sample file based on all layers that are found in the top
> > directory. It also creates a local.conf.sample file by combining
> fragment
> > files in the layers (i.e., local.conf.sample.XX where XX is a number
> > between 00 and 99). The local.conf.sample from meta-poky is considered
> > to have XX == 50. The reason for this is that we quickly realized that
> > the static templateconf directory setup was unusable for us when we
> > want to be able to use layers in different combinations.
> 
> Cheers. I'd say if you need to place lots of customizations into

There actually isn't lots of configuration in those fragments. 

> local.conf that's not a recommended setup to begin with: as said
> elsewhere it should have precisely two definitions: distro and
> machine, and nothing else. What kind of things are in those fragments?

In our BSP layer there is some configuration we want even if our 
distro layer is not used (e.g., SSTATE_DIR). It also sets a default 
MACHINE that matches one from our BSPs. In the distro layer, it sets 
DISTRO. It also adds some extra, commented variables that our users 
may want to enable in their local.conf files, much like the examples 
in the local.conf.sample from meta-poky.

Part of this is of course related to that we use repo to fetch the 
layers we need and thus we do not have the luxury of bitbake specific 
tools like kas and whisk that can add bitbake configuration in addition 
to the actual layers. On the other hand, our environment is very similar 
to the default experience with poky from a user's perspective.

> Should they be consolidated in machine and distro definitions?
> 
> Alex

//Peter