Re: [PATCH] scripts: merge_config: Add flag to prevent unsetting config option

[Masahiro Yamada]

On Mon, Aug 14, 2023 at 12:00 AM Rahul Rameshbabu
<sergeantsagara@xxxxxxxxxxxxxx> wrote:
>
>
> On Tue, 08 Aug, 2023 04:04:37 +0900 "Masahiro Yamada" <masahiroy@xxxxxxxxxx> wrote:
> > On Mon, Aug 7, 2023 at 1:13 PM Rahul Rameshbabu
> > <sergeantsagara@xxxxxxxxxxxxxx> wrote:
> >>
> >>
> >> On Sun, 06 Aug, 2023 23:19:55 +0900 "Masahiro Yamada" <masahiroy@xxxxxxxxxx> wrote:
> >> > On Sun, Jul 30, 2023 at 6:42 AM Rahul Rameshbabu
> >> > <sergeantsagara@xxxxxxxxxxxxxx> wrote:
> >> >>
> >> >> Overriding a previously defined entry for a config option with 'is not set'
> >> >> may be undesirable in some fragment configuration setups.
> >> >
> >> > Then, you should remove the 'is not set' entry from the fragment.
> >>
> >> I had a feeling that was the expectation. Just for reference, my flow
> >> for generating fragments looks like the following.
> >>
> >>   1. make allnoconfig
> >>   2. make menuconfig   # select the options that I desire for the fragment
> >
> >
> > Sorry, I could not understand
> > how these steps generate a fragment file.
> >
> > You will get a full .config file
> > after 'make menuconfig'.
>
> Yep, this is right. I am not really generating a fragment this way but
> rather full configs with minimal options that I end up wanting to merge
> together. What's your process for generating fragments you need? Just
> dumping the options you want in fragment files and letting make properly
> select the dependencies?


I would manually write a fragment file.


I see comment lines in

kernel/configs/debug.config
kernel/configs/xen.config

I believe they were written by hand.





-- 
Best Regards
Masahiro Yamada