Skip parsing of transitional keyword #30
Conversation
Signed-off-by: Quirin Gylstorff <[email protected]>
This allows to parse configs with the transitional key word. For a working version of the transitional feature it is necessary to extend parsing of the default keyword to support setting the value to a variable: ``` config NEW_BOOL bool "New bool option" default OLD_BOOL ``` Signed-off-by: Quirin Gylstorff <[email protected]>
There was a problem hiding this comment.
Thanks for this contribution.
However, i'm not immediately convinced that we should just silence / ignore the transitional keyword.
Skipping the transitional keyword means that the symbol holding this keyword suddenly becomes a valid symbol again, which potentially can enter the .config file.
Also it seems that this silencing will allow invalid config descriptions, such as having prompts on settings with the transitional keyword.
I do understand the wish for being able to parse Kconfig trees having transitional attribute, but when supporting / silencing this attribute then we should not allow invalid Kconfig files in that same process.
If not supporting the attribute but still allowing it to be present, then such implementation should still ensure the symbol does not become or behave like a regular Kconfig symbol, which unfortunately would be the case with this PR.
I hope to find time to look into proper support for transitional.
2 participants
This skips the transitional keyword to allow parsing of kernel config of Linux kernel => 6.18. It does not implement the transitional feature as this requires additional changes.
Also add the test files to .gitignore.
This fixes #25.