summaryrefslogtreecommitdiffstats
path: root/meta/classes/kernel.bbclass
diff options
context:
space:
mode:
authorChristopher Larson <chris_larson@mentor.com>2012-05-15 20:26:25 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-05-17 21:13:08 +0100
commit0c7720027b5333d96d349a24ba1dfc9967155331 (patch)
treefa66d89a8e7fe4a828f279a19445d9aaa3b56a11 /meta/classes/kernel.bbclass
parentcaee06405f90d44b3476af645e2b3918578ba6b9 (diff)
downloadpoky-0c7720027b5333d96d349a24ba1dfc9967155331.tar.gz
oe.types: give the regex type more sane semantics
Currently, if a variable is unset or has an empty value, the regex type will return a match object which always matches. Not all variable types will necessarily have the same behavior for handling defaults. I believe that returning a match object which matches nothing when a variable is unset is superior to returning one which matches anything, and the user can always explicitly request anything via '.*', if that's what they want. This constructs a null pattern object which will never match, and uses it when encountering an unset or empty variable (currently, these two things are one and the same, as maketype is handling the default. we may well want to shift that logic into the individual types, giving them more control over default behavior, but currently the behavior is at least relatively consistent -- no difference between unset and empty variables). (From OE-Core rev: dc7e4a79d9a1884b4c5705ef3173613958204b50) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/kernel.bbclass')
0 files changed, 0 insertions, 0 deletions