diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-07-25 19:03:08 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-07-26 10:49:13 +0100 |
commit | 5c09cbe3bf456e968fc853827698eb18b62e8348 (patch) | |
tree | 34250e2aeaa73bf72b78957cfcb6c4c240d380be /meta/recipes-multimedia/flac | |
parent | f10a3457cdfbb4a94978da998d178d4254632fa7 (diff) | |
download | openembedded-core-5c09cbe3bf456e968fc853827698eb18b62e8348.tar.gz openembedded-core-5c09cbe3bf456e968fc853827698eb18b62e8348.tar.bz2 openembedded-core-5c09cbe3bf456e968fc853827698eb18b62e8348.tar.xz openembedded-core-5c09cbe3bf456e968fc853827698eb18b62e8348.zip |
lib/oe/utils: 'Fix' oe.utils.contains() behaviour
Currently oe.utils.contains(X, "A", true, false) will return true for substring matches,
e.g. if X = "ABC". This is not what most users expect from the function.
In the common OE use of this function there is the case of "touchscreen" and "screen" being
used as independent variables. Whilst it could be argued there isn't a problem in that
specific case (touchscreens are usually on screens), there is no substring usage of this
function is OE-Core so this patch changes the behaviour to match only full strings.
It also fixes a bug where duplicate entries would confuse multiple matches, e.g.
contains(X, ["A", "B"], ...) would match X = "A A" which is clearly wrong.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-multimedia/flac')
0 files changed, 0 insertions, 0 deletions