diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-07-18 12:59:15 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-07-30 14:38:30 +0100 |
commit | f2d2136dbb3730abb87699ce03dd54c27ebb7833 (patch) | |
tree | 27c407e9a955d6dec7b26d6402372b169a0b6da4 /bitbake/lib/layerindexlib/cooker.py | |
parent | 7d3fb188bfe4dc9aebe80286a65b357ed2ae8b8f (diff) | |
download | poky-f2d2136dbb3730abb87699ce03dd54c27ebb7833.tar.gz |
bitbake: data_smart/parse: Allow ':' characters in variable/function names
It is becomming increasingly clear we need to find a way to show what
is/is not an override in our syntax. We need to do this in a way which
is clear to users, readable and in a way we can transition to.
The most effective way I've found to this is to use the ":" charater
to directly replace "_" where an override is being specified. This
includes "append", "prepend" and "remove" which are effectively special
override directives.
This patch simply adds the character to the parser so bitbake accepts
the value but maps it back to "_" internally so there is no behaviour
change.
This change is simple enough it could potentially be backported to older
version of bitbake meaning layers using the new syntax/markup could
work with older releases. Even if other no other changes are accepted
at this time and we don't backport, it does set us on a path where at
some point in future we could
require a more explict syntax.
I've tested this patch by converting oe-core/meta-yocto to the new
syntax for overrides (9000+ changes) and then seeing that builds
continue to work with this patch.
(Bitbake rev: aa9f7b80cfdb1119050af469a07ebd949829026c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/layerindexlib/cooker.py')
0 files changed, 0 insertions, 0 deletions