PTU5KAS/kas
Claudius Heine 95015045db implementation of environment variable passthrough
With this its possible to create custom environment variables within the kas
configuration file, that are passed through to the build environment:

    env:
      VARIABLE_NAME: "default variable value"

Those variables can be overwritten by variables of the environment kas is
started in:

    $ VARIABLE_NAME="overwritten variable value" kas shell ...

Those variables are also added to the 'BB_ENV_EXTRAWHITE' variable list to make
them available to bitbake.

This is useful for instance storing sensitive information, that should not be
part of the configuration files or bitbake recipes.

Signed-off-by: Claudius Heine <ch@denx.de>
2017-11-24 10:19:12 +01:00
..
__init__.py config: Added schema validation for configuration files 2017-10-13 14:11:10 +02:00
__main__.py entry: Consistently call python3 2017-08-31 22:31:41 +02:00
__version__.py implementation of environment variable passthrough 2017-11-24 10:19:12 +01:00
build.py config: Implemented multi-target support 2017-10-13 14:11:00 +02:00
config.py implementation of environment variable passthrough 2017-11-24 10:19:12 +01:00
configschema.py implementation of environment variable passthrough 2017-11-24 10:19:12 +01:00
includehandler.py includehandler: remove possible duplicates from the missing_repos list 2017-10-18 10:04:06 +02:00
kas.py kas: added version output when starting kas 2017-10-19 17:15:26 +02:00
libcmds.py multiconfig: implement initial support 2017-11-08 09:42:56 +01:00
libkas.py implementation of environment variable passthrough 2017-11-24 10:19:12 +01:00
repos.py Fixed issues that occured with pylint 1.7.2 2017-06-28 15:10:14 +02:00
shell.py config: Implemented multi-target support 2017-10-13 14:11:00 +02:00