Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v12.9.0 2019-06-03T04:50:06Z 2019-06-03T04:50:06Z Ulf Magnusson ulfalizer@gmail.com 2019-06-02T16:15:59Z urn:sha1:55bc8c380869ea663092212e8fe388ad7abae596 Hardcoding load_config() and write_(min_)config() to write any message to stdout is awkward, because it means that the message can't be easily reused when stdout is the wrong place to write it to (e.g. in menuconfig/guiconfig). This gets extra bad now that there's also the "No change to ..." message. Modify load_config() and write_(min_)config() to return the message as a string instead, and have them always return a message, instead of just when 'filename' is None and verbose=True. This makes things flexible and straightforward. Use the new behavior in menuconfig.py and guiconfig.py. They now show "No change to ..." when saving a file doesn't modify it. Tools that want to write messages to stdout should now do print(kconf.load_config()) / print(kconf.write_config()). There's no clean way to preserve perfect backwards compatibility here, but keep accepting the 'verbose' argument and print a deprecation warning if a value is ever passed for it. That way, scripts will keep running, though possibly with less output on stdout. This changes the meaning of the load_config() return value as well, though I suspect it was only ever used by the menuconfig/guiconfig interfaces. The new behavior applies for kconfiglib.VERSION >= (12, 0, 0). 2019-04-27T13:09:08Z Ulf Magnusson ulfalizer@gmail.com 2019-04-27T12:16:10Z urn:sha1:4f1674fc32224003931af4a74aa18168786ec9a2 Simple script for initializing the configuration from an existing configuration file (usually a minimal configuration). Just copying the minimal configuration to .config would usually work, due to Kconfig semantics, but having it be a full configuration file from the start might be handier and less confusing.