[Buildroot] Development flow to track .config

[Buildroot] Development flow to track .config

[Ramon Crichlow]

[-- Attachment #1.1: Type: text/plain, Size: 611 bytes --]

What would be best practice for saving changes to the top level .config
file using a private git repo?

The issue is that since .config is listed in .gitignore , git will not
track changes to .config.  Secondly if make [config file] is run, changes
will be lost.

Assume that

# make abc_defconfig

was used to initially create .config

Is the following flow best practice?  If not please suggest a better one.

1.  Make a change to .config using make menuconfig
2.  Diff the change between .config and .config.old
3.  Edit abc_defconfig to mirror the changes in step 2
4.  Commit abc_defconfig

Regards,
Ramon

[-- Attachment #1.2: Type: text/html, Size: 863 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] Development flow to track .config

[Edgar Bonet]

Hello!

Ramon Crichlow wrote:
> Is the following flow best practice?  If not please suggest a better one.
>
> 1.  Make a change to .config using make menuconfig
> 2.  Diff the change between .config and .config.old
> 3.  Edit abc_defconfig to mirror the changes in step 2
> 4.  Commit abc_defconfig

Not sure it's the best, but here is what I do:

1. git switch -c 'my-custom-branch'
2. make some_board_defconfig
3. make nconfig # or your preferred variant of menuconfig, save and exit
4. make savedefconfig # this will save the relevant changes to some_board_defconfig
5. git commit -a -m 'My custom changes to some_board_defconfig'

Best regards,

Edgar.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] Development flow to track .config

[Ramon Crichlow]

[-- Attachment #1.1: Type: text/plain, Size: 830 bytes --]

Didn't know about make savedefconfig - thanks!

Ramon

On Tue, Jan 31, 2023 at 3:36 PM Edgar Bonet <bonet@grenoble.cnrs.fr> wrote:

> Hello!
>
> Ramon Crichlow wrote:
> > Is the following flow best practice?  If not please suggest a better one.
> >
> > 1.  Make a change to .config using make menuconfig
> > 2.  Diff the change between .config and .config.old
> > 3.  Edit abc_defconfig to mirror the changes in step 2
> > 4.  Commit abc_defconfig
>
> Not sure it's the best, but here is what I do:
>
> 1. git switch -c 'my-custom-branch'
> 2. make some_board_defconfig
> 3. make nconfig # or your preferred variant of menuconfig, save and exit
> 4. make savedefconfig # this will save the relevant changes to
> some_board_defconfig
> 5. git commit -a -m 'My custom changes to some_board_defconfig'
>
> Best regards,
>
> Edgar.
>

[-- Attachment #1.2: Type: text/html, Size: 1247 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] Development flow to track .config

[Arnout Vandecappelle]

On 31/01/2023 22:36, Edgar Bonet wrote:
> Hello!
> 
> Ramon Crichlow wrote:
>> Is the following flow best practice?  If not please suggest a better one.
>>
>> 1.  Make a change to .config using make menuconfig
>> 2.  Diff the change between .config and .config.old
>> 3.  Edit abc_defconfig to mirror the changes in step 2
>> 4.  Commit abc_defconfig
> 
> Not sure it's the best, but here is what I do:
> 
> 1. git switch -c 'my-custom-branch'
> 2. make some_board_defconfig
> 3. make nconfig # or your preferred variant of menuconfig, save and exit
> 4. make savedefconfig # this will save the relevant changes to some_board_defconfig

  If you want to start from scratch instead of an existing defconfig, or if you 
want to save with a different filename, you can use

make savedefconfig BR2_DEFCONFIG=/path/to/defconfig/file

  Regards,
  Arnout


> 5. git commit -a -m 'My custom changes to some_board_defconfig'
> 
> Best regards,
> 
> Edgar.
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot