poky oe-init-build-env doesn't update local.conf with changes from local.conf.sample


Andy Basey
 

I have an existing build with packages defined in my own layer outside the build directory in the local.conf.sample
I want to add a package so I add it to my local.conf.sample and then source oe-init-build-env again
It doesn't overwrite the local.conf in poky/build/conf as it already exists

Is there a preferred way to make it update?
Or do I just need to manually delete the files in that directory and then run source oe-init-build-env?
I don't want to delete the whole build directory as it takes far too long to do it again from scratch

For reference I am using the local.conf.sample because that is my source controllable config file


 

On Tue, 10 Nov 2020 at 09:56, Andy Basey <a.basey@landguardsystems.com> wrote:

I have an existing build with packages defined in my own layer outside the build directory in the local.conf.sample
I want to add a package so I add it to my local.conf.sample and then source oe-init-build-env again
It doesn't overwrite the local.conf in poky/build/conf as it already exists

Is there a preferred way to make it update?
Or do I just need to manually delete the files in that directory and then run source oe-init-build-env?
I don't want to delete the whole build directory as it takes far too long to do it again from scratch

For reference I am using the local.conf.sample because that is my source controllable config file
If you're adding packages to an image, the best thing to do is to
create your own image recipe and put that in your layer (so it will be
under version control).

--
Paul Barker
Konsulko Group