summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/python/python3-numpy
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2021-11-13 16:19:49 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2021-11-15 11:03:25 +0000
commitf07a097213477c4e4291e6dbcddd04300631f294 (patch)
tree5b424696cded82a6f469ed79a6080139c98535a4 /meta/recipes-devtools/python/python3-numpy
parent119c592530e82ab2a9bdddb532640c345b58cf8b (diff)
downloadpoky-f07a097213477c4e4291e6dbcddd04300631f294.tar.gz
bitbake: cache/ConfHandler: Drop TOPDIR/chdir manipulations
This code has been unchanged since 2006 apart from attempts to optimise performance by minimising chdir() calls. There is no reason the modern bitbake parser should be changing directory all the time. We did have some path assumptions in the mists of time but those were resovled and the code is deterministic and doesn't depend on cwd now for parsing. We can therefore drop the changes in directory. Also, TOPDIR is now being set by cookerdata in all cases so we don't need the fallbacks in this code (which was used to effectively initialise a value). We don't need to change TOPDIR when parsing a recipe, that makes no sense. If we stop all the other messing around, we don't need to expand TMPDIR either. These changes have the potential to break some obscure use cases such as an anonymous function assuming the current working directory, or some case which depends on TOPDIR changing but I believe any such uses should be fixed at this point. (Bitbake rev: add5d488e1d6607a98441836075d01cb1dc9c0fa) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/python/python3-numpy')
0 files changed, 0 insertions, 0 deletions