Kconfiglib.git, branch v10.19.1

Make 10.19.1 release

2018-11-02T02:53:49Z

Adds fixes for two obscure crashes, related to consecutive empty if's and toggling symbols without a type in the menuconfig: - Commit 0e6cd82 ("Fix removal of multiple consecutive 'if' nodes") - Commit db60270 ("menuconfig: Fix crash when toggling symbols without a type")

menuconfig: Fix crash when toggling symbols without a type

2018-11-02T02:53:02Z

Trying to toggle the following symbol crashed the menuconfig: config FOO prompt "foo" Symbols defined without a type are pointless and generate a warning (particular definition locations can omit the type, but some definition location should give a type if the symbol is defined in multiple locations). We should never crash for them though. Fix the crash. The code assumed that the symbol's current value would appear in Symbol.assignable, like for a visible bool/tristate, but symbols without types get their name as their value. Also skip printing "(NEW)" next to symbols without a type.

Fix removal of multiple consecutive 'if' nodes

2018-11-02T02:52:46Z

Despite 'if' nodes being flattened before 'if' removal, consecutive 'if' nodes can still show up for code like the following: ... if X endif if X endif ... _remove_ifs() failed to remove the second 'if' node, leading to a crash e.g. when turning on show-all mode in the menuconfig in a menu with such code (due to the unexpected 'if' node). Stuff like the above could potentially result from 'osource's with no matches, though I just spotted the error while looking over the code. Fix the 'if' removal logic to properly handle consecutive 'if' nodes.

Make 10.19.0 release

2018-11-01T02:59:18Z

Adds commit 8be38f2 ("Don't show backtraces for expected exceptions in tools"), which hides backtraces for expected errors from tools (like Kconfig syntax errors and missing files).

Don't show backtraces for expected exceptions in tools

2018-11-01T02:21:09Z

KconfigError and IOError are part of normal operation and don't indicate a problem with the library itself. Catch and print them in standard_kconfig() and sys.exit(), to avoid spammy backtraces from e.g. menuconfig.py when Kconfig files don't exist or have errors.

Refactor _remove_ifs()

2018-11-01T00:18:38Z

Can get away with a single variable by assigning node.list earlier, and save a tiny bit of work with a chained assignment. Also clarify what the tricky Python chained assignments correspond to, where it matters.

menuconfig: Add quotes around filename for .config loading errors

2018-11-01T00:02:32Z

Turns into a weird-looking 'Error loading ' otherwise. Maybe Enter should be ignored for empty filenames instead...

Make 10.18.0 release

2018-10-31T00:31:32Z

Commit 14603c0 ("Make errno/strerror/filename available on IOError") makes IOError/OSError.errno/strerror/filename available to scripts, when it is raised from e.g. Kconfig.load_config(). Previously, some implementation trickery related to custom exception messages meant that they weren't available.

Make errno/strerror/filename available on IOError

2018-10-30T23:02:43Z

An error reporting flaw was that most raised IOErrors got their errno/strerror/filename fields stripped, due to wanting to show a custom messages. The problem was that adding back 'errno' and 'strerror' made IOError.__str__() always return a fixed string ("[Errno ] "), ignoring any custom message. This is friendly to users, but unfriendly to scripts (the menuconfig had a workaround). Make things friendly to both by raising an internal subclass of IOError instead, that preserves errno/strerror/filename but prints a custom message. The exception can then still be caught as IOError/OSError by scripts.

Simplify _INIT_SRCTREE_NOTE definition

2018-10-30T22:02:20Z