Richard Purdie <richard.purdie@...> writes: When you really feel that this Yoda style naming must be fixed; then ok. But for me, the gain would not be large enough to break the

I fixed that typo, thanks for reporting. Cheers, Richard

This reverts commit 6184b56a7a0fc6f5d19fdfb81e7453667f7da940. The above commit breaks building of recipes where sources are checked out from Git and PATCHTOOL = "git". The do_patch tasks fails

An automated conversion using scripts/contrib/convert-spdx-licenses.py to convert to use the standard SPDX license identifiers. Two recipes in meta-selftest were not converted as they're that way

We're standardising on SPDX license names so it is overdue to change the ones in the LICENSE fileds to the SPDX values. Add a conversion script which makes this straightforward on the most

If you provide ASFLAGS CMake will already load them into CMAKE_AS_FLAGS anyway, they will just not be force-overriden. Martin Am 17.02.22 um 20:46 schrieb Khem Raj:

We did try and make some of the names better describe what the variables do and make the variables more consistent. For example, a reference to HASHBASE was changed to BASEHASH which better matches

<enrico.scholz=sigma-chemnitz.de@...> wrote: Enrico, cut this out please. Every time you start with a specific, kind of valid, question, then turn it into a rant about how the

Hello, +layer maintainers to ensure they see that. -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com

Richard Purdie <richard.purdie@...> writes: s/descriptive/politically correct/ True; because it does not make sense, these variables should not be named in this way. The renamed

wrote: Just as a warning, the code is actually confused. The base.bbclass code assumes it is a recipe name, the license_image code assumes it is a package name. All the more reason to come up with a

We need to be mindful that we need to resolve this to unblock the other language changes and feature creep here is potentially problematic. I do think it is worth trying to improve things rather than

wrote: Whilst you could say they sound like booleans, they clearly can't be as that wouldn't make sense, e.g. "Ignoring variables in basehash" makes no sense. Secondly, most metadata variables are

"Saul Wold" <Saul.Wold@...> writes: again: most of these renamings make identifiers much less descriptive because they now sound like boolean flags instead of lists Enrico

The [3] should be https://git.openembedded.org/openembedded-core/commit/?id=311e61ae14b7216f5b98f1afe0e791644a07c9d0 that's where LAYERSERIES_CORENAMES was changed to kirkstone (it's not due to

Updates within bitbake now require this call to be triggered somewhere with floating git source revs. Add the missing call. Issue can be reproduced with: devtool check-upgrade-status

This patch adds a fix for a crash in grub's script handling. It is a part of a security series [1]. [1] https://lists.gnu.org/archive/html/grub-devel/2021-03/msg00007.html Signed-off-by: Marta

This patch adds a fix for a NULL pointer dereference in grub's commands/ls. It is a part of a security series [1]. [1]

This patch adds a fix for a NULL pointer dereference in grub's script/execute. It is a part of a security series [1]. [1]

This patch adds a fix for an incorrect use of a negative value in grub's util/glue-efi. It is a part of a security series [1]. [1]