diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-10-03 16:11:02 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-10-07 22:31:08 +0100 |
commit | f2a14d7ca083767f8d6607aa24c1911a715a4f9e (patch) | |
tree | 35374071e02b94c1f6fc6b5bac5149dfd23f7681 /scripts/lib/checklayer/cases/bsp.py | |
parent | f43b8f2f77bb6fbedbabfa40ddfd29b8f8891273 (diff) | |
download | poky-f2a14d7ca083767f8d6607aa24c1911a715a4f9e.tar.gz |
bitbake: ast: Fix fragment behaviour with overrides
Imagine a machine fragment machine/A and a configuration which sets:
MACHINE = "B"
MACHINE:forcevariable = "C"
As I understand it, the fragment behaviour was intended to replace the
MACHINE = "B", so the override would still be active. The current code
replaces all variable overrides.
parsing=True, switches to the other behaviour, which I believe was the
design intent and the behaviour users would expect.
This is useful to allow test configurations to override a MACHINE setting
without change the fragments which would complicate the test code.
(Bitbake rev: 6b4882a55567d440713ee34d81810167cd958d56)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/lib/checklayer/cases/bsp.py')
0 files changed, 0 insertions, 0 deletions