On Fri, 15 Jul 2022 at 23:57, Alexandre Belloni
wrote:
> I don't think you need a custom script for site.conf, it is searched for
> relative to BBPATH? I usually just put it directly as conf/site.conf in
> the custom layer so it is in version control and not copied to BUILDDIR.
I was thinking of
On 15/07/2022 18:00:57+0200, Alexander Kanavin wrote:
> On Fri, 15 Jul 2022 at 16:42, Richard Purdie
> wrote:
> > We'd always intended that site.conf was more something the user would
> > setup once for their environment and not need to change. It was
> > therefore deliberately left out of the
On Fri, 15 Jul 2022 at 18:24, Richard Purdie
wrote:
> In that sense, it was something a user would provide, not something
> that would be provisioned by automated scripting. If there are settings
> to be provisioned by a layer, we have local.conf for that? Why do we
> need another file too?
On Fri, 2022-07-15 at 18:15 +0200, Alexander Kanavin wrote:
> On Fri, 15 Jul 2022 at 16:42, Richard Purdie
> wrote:
> > We'd always intended that site.conf was more something the user would
> > setup once for their environment and not need to change. It was
> > therefore deliberately left out of
On Fri, 15 Jul 2022 at 16:42, Richard Purdie
wrote:
> We'd always intended that site.conf was more something the user would
> setup once for their environment and not need to change. It was
> therefore deliberately left out of the auto-setup piece.
I don't think I understand this point in
On Fri, 15 Jul 2022 at 16:42, Richard Purdie
wrote:
> We'd always intended that site.conf was more something the user would
> setup once for their environment and not need to change. It was
> therefore deliberately left out of the auto-setup piece.
> I hadn't remembered we have an sample version
On Wed, 2022-07-06 at 20:23 +0200, Alexander Kanavin wrote:
> This allows:
>
> 1. Showing users where and how to define these settings correctly when
> setting up
> a build from templates in poky (meta-poky/conf/site.conf.sample has commented
> out examples and was previously unused).
>
> 2.
> -Original Message-
> From: Alexander Kanavin
> Sent: den 7 juli 2022 16:48
> To: Peter Kjellerstedt
> Cc: openembedded-core@lists.openembedded.org; Alexander Kanavin
>
> Subject: Re: [OE-core] [PATCH 1/2] scripts/oe-setup-builddir: copy
> site.conf.sample out
On Thu, 7 Jul 2022 at 16:38, Peter Kjellerstedt
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
: 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:45, Peter Kjellerstedt
> wrote:
>
> > > Setting up a build directory from standard poky
> > > or oe-core
On Thu, 7 Jul 2022 at 15:45, Peter Kjellerstedt
wrote:
> > 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
> -Original Message-
> From: Alexander Kanavin
> Sent: den 7 juli 2022 15:36
> To: Peter Kjellerstedt
> Cc: openembedded-core@lists.openembedded.org; Alexander Kanavin
>
> Subject: Re: [OE-core] [PATCH 1/2] scripts/oe-setup-builddir: copy
> site.conf.sample out
On Thu, 7 Jul 2022 at 15:26, Peter Kjellerstedt
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
>
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Alexander Kanavin
> Sent: den 6 juli 2022 20:23
> To: openembedded-core@lists.openembedded.org
> Cc: Alexander Kanavin
> Subject: [OE-core] [PATCH
This allows:
1. Showing users where and how to define these settings correctly when setting
up
a build from templates in poky (meta-poky/conf/site.conf.sample has commented
out examples and was previously unused).
2. Distributing site-specific settings with template configurations in other
15 matches
Mail list logo
