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 15:36
> 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 15:26, Peter Kjellerstedt
> <peter.kjellerstedt@axis.com> wrote:
> 
> > While I can't speak for others, this change will break our build environment.
> > We have a global site.conf file in an NFS directory that everyone use. It
> > contains all proxy settings and similar that are required to build inside the
> > corporate environment. Copying a dummy site.conf file into the local build
> > directory will prevent the global file from being used.
> 
> Then you need to create a configuration template that is specific to
> your company first, and there's a convenient command to do that
> provided in patch 2/2.

While I haven't actually tried your new command, based on what you and 
others have written, it does not at all seem compatible with how our 
environment is setup and what it expects from poky. :(

> Setting up a build directory from standard poky
> or oe-core templates (which I presume is how you set up builds) does
> not hold a promise that what is being copied will not change in
> potentially breaking ways.

While I may be able to fix the environment for builds that use some of 
our layers, setting up pure poky builds will no longer work without 
manual intervention.

> Alex

//Peter