when savedefconfig decides what to write out, what does it do for things
that are not at the default, but were set to not be default as part of
dependancy resolution?
David Lang
On Fri, Aug 06, 2010 at 08:25:43PM -0700, [email protected] wrote:
> when savedefconfig decides what to write out, what does it do for things
> that are not at the default, but were set to not be default as part of
> dependancy resolution?
The short version:
Any symbol that does not have default value are written to
the defconfig file.
Using the defconfig file as input or using the full config file
as input shall result in the same configuration.
If not you found a bug we need to fix.
Arve found one bug I have to look into - pending feedback.
And I have found one bug related to tristate choice values.
So a bit work is needed to make it ready :-(
But it works for most of the defconfig we have today.
Sam
On Sat, 7 Aug 2010, Sam Ravnborg wrote:
> On Fri, Aug 06, 2010 at 08:25:43PM -0700, [email protected] wrote:
>> when savedefconfig decides what to write out, what does it do for things
>> that are not at the default, but were set to not be default as part of
>> dependancy resolution?
>
> The short version:
> Any symbol that does not have default value are written to
> the defconfig file.
>
> Using the defconfig file as input or using the full config file
> as input shall result in the same configuration.
> If not you found a bug we need to fix.
Ok, so I take this to mean that if selecting one symbol forces selection
of another, then both symbols will be written to the defconfig file, even
though only the first would be needed to recreate the full file.
this is a wonderful step forward, I'm just trying to understand the
nuances of it.
David Lang
> Arve found one bug I have to look into - pending feedback.
> And I have found one bug related to tristate choice values.
>
> So a bit work is needed to make it ready :-(
> But it works for most of the defconfig we have today.