The certificates and keys are stored in a repository and taken from there.
It is a neative repository that puts the keys into the sysroot where other
recipes can take them
All the key related scripts where deleted or put in the development-keys
repository.
Basic simplifications where done, there is yet still room for improvement.
To make images compatible with each other for development a comon set of keys
will be used. The keys are located on k-stufen.
* add script to download and extract keys
* adjustments to coreos-init-build-env script
* adjustments to check_files_exist function
The devtool plugin offer a high level integration with Bitbake and
thus is under GPLv2 license.
The coreos-device script is a low level scripts that implement all
the functionality and is not under GPLv2
there might be OS where usr merge is not included and thus
/bin/env is not available as it resides in /usr/bin/env.
Signed-off-by: Marc Mattmueller <marc.mattmueller@netmodule.com>
This fix the recipes by ihneriting the python3native class. DEPENDS
was also fix, as we need the native version of the needed package
and not the one from the target. It was previously only building
because bitbake use by default the host python3 and on my computer
I was having all the deps locally installed.