[Buildroot] [RFC 1/1] support/kconfig: Allow to override 'default' config property
petr.vorel at gmail.com
Sun Apr 7 18:38:35 UTC 2019
> > Really, the defconfig *is* the place where defaults are overriden.
> > For example, at work, I handle a single br2-external for two "projects"
> > that each have four "boards", and each have three configurations. There
> > is no way your proposal can cover this.
> > Alternatively, what you propose is just pushing the feature of a
> > defconfig into the language itself. I don't think this is a good idea.
> > Even more so, as your proposal does not address all the cases either:
> > it only catters for strings, but what about choices, tri-states?
> > So, I'll be harsh, but NAK.
> FWIW, I completely agree with Yanns points. Having two ways of
> configuring this (defconfigs and br2-external trees) makes things more
> complicated for little added value.
Also agree with Yann and Peter.
More information about the buildroot