summaryrefslogtreecommitdiffstats
path: root/meta-extras/packages/python/python-2.5.2/autohell.patch
diff options
context:
space:
mode:
authorAlexander Kanavin <alex@linutronix.de>2025-11-04 11:08:01 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-11-04 13:16:04 +0000
commit5d7abe740e26a34216236e0b00f6d2bc001e3156 (patch)
treea48e9294d1acc3c5307f3acbda188cb32ca5ed7f /meta-extras/packages/python/python-2.5.2/autohell.patch
parent07c35eec54153f3aab0501aa880dfc8824ccb08b (diff)
downloadpoky-master.tar.gz
bitbake: bitbake-setup: rename 'build' -> 'setup'HEADmaster
After a terminology review by Antonin we brainstormed something less confusing than 'build' and 'build directory' for the place where bitbake-setup clones layers and creates a *bitbake* build directory in. People are bound to get these two confused and mix them up, and 'setup' is much more distinct and aligns nicely with 'bitbake-setup'. It's also not claimed by anything else in OE/Yocto. So before: top-dir -> build-dir (can be several) -> bitbake build dir, layer dir, config dir Now: top-dir -> setup-dir (can be several) -> bitbake build dir, layer dir, config dir This also updates the respective command line options, I understand it's a breaking change, but as before the tweaks are simple and we need to get the terminology right for the users, and now is the time to do it. (Bitbake rev: eeb81a35bf0304451f7612950d5156ea7ff18bad) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-extras/packages/python/python-2.5.2/autohell.patch')
0 files changed, 0 insertions, 0 deletions