summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/parse/parse_py/BBHandler.py
diff options
context:
space:
mode:
authorNikolai Merinov <n.merinov@inango-systems.com>2025-02-04 09:13:46 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-02-05 12:11:01 +0000
commitb65452bda3cadf53b2a262df3eb43adea88d2401 (patch)
treecfcb0fb00cb70dca246492e60ee6e1603428b67f /bitbake/lib/bb/parse/parse_py/BBHandler.py
parentc2da016918d1fda5bf63d94b59863f5013e482f9 (diff)
downloadpoky-b65452bda3cadf53b2a262df3eb43adea88d2401.tar.gz
bitbake: parse: Forbid ambiguous assignments to ${.}, ${+}, and ${:} variables
Old code that parse variable names in assignment commands behave differently for variables that ends with special symbol for single-character variable names and multi-character variable names. For example: A+="1" # Change variable ${A}, '+' glued to '=' A+ = "1" # Change variable ${A+} +="1" # Change variable ${+}, the '+' symbol not part of assignment operator + = "1" # Change variable ${+} New code would always assume that '.=', '+=', and ':=' is assignment operator. As result code like the following would raise parsing error +="value" While code with extra spaces would work as before + = "value" # Change variable ${+} This change allow to catch issues in code that generate bitbake configuration files in a manner like "echo ${VARNAME}+=${VALUE} >> conf/local.conf" (Bitbake rev: 93059aad13a12cd69d86368795c88e5349197d5d) Signed-off-by: Nikolai Merinov <n.merinov@inango-systems.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/parse/parse_py/BBHandler.py')
0 files changed, 0 insertions, 0 deletions