On Wed, Oct 28, 2015 at 09:42:01AM +0900, Olof Johansson wrote:
Somewhat wide distribution list here, since I've added everyone who's
touched the script, with the presumption that those have been the major
users of it. Please make sure none of these changes break your use cases.
+Bruce. I think you were going to test these with the linux-yocto tooling. Did
you get a chance to run that test? I'd like your thoughts on the two comments
I've done some reworks of merge_config.sh. I was quite hesitant to start
this since there are no good ways to see if your changes break others
or not, so the first thing I did was to add some tests. I know this is
highly unorthodox so try not to panic. :-)
As far as what this series does is:
- Adds a way to pass in CONFIG_FOO=<value> on the command line, it gets
treated as a single-entry fragment file
- The script now prints the warnings on stderr, and returns non-0 when
something is encountered
This one might impact linux-yocto usage, Bruce? That said, it seems like the
right thing to do. So I'd still like to see it go in, but we may need to plan to
update the dependent tooling to use it.
- Optionally, it'll also return non-0 when a redundant entry is found. I
presumed people rely on -r not being a failure so I did this separately
- CONFIG_FOO=n and "# CONFIG_FOO is not set" is now treated the same,
and using the former doesn't cause an invalid warning when the results
are checked at the end
- Slightly odd things happened if a fragment contains the same option
twice: It'd produce a warning that was malformed. Now just ignore that
and use only the latest value of said option.
This one will likely impact usage as well. linux-yocto does want to report when
there is an override, not as an error, but for informational purposes - "Where
does my option get clobbered?"