3e0dd10416
This patch adds the top-level `overrides` entry, which is used to override (or pin) the refspec of repositories. The main difference to a direct override is that this logic only applies to repos that are already defined. By that, a superset of all repos can be added to this entry (similar to a global lockfile), but only the currently active ones are affected. A new top-level keyword is required because everything below the "repos" keyword is potentially defined by "default" values. For the locking mechanism, a clear separation between overrides (only override if existing) and definitions is required to be able to define a global lockfile with all possible repos, while just defining some repos. Proposed-by: Ross Burton <ross@burtonini.com> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com> [Jan: also bump __file_version__] Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Setup tool for bitbake based projects ===================================== +--------------------+ | Build Status | +====================+ | |workflow-master|_ | +--------------------+ | |workflow-next|_ | +--------------------+ .. |workflow-master| image:: https://github.com/siemens/kas/workflows/master/badge.svg .. _workflow-master: https://github.com/siemens/kas/actions?query=workflow%3Amaster .. |workflow-next| image:: https://github.com/siemens/kas/workflows/next/badge.svg .. _workflow-next: https://github.com/siemens/kas/actions?query=workflow%3Anext This tool provides an easy mechanism to setup bitbake based projects. The OpenEmbedded tooling support starts at step 2 with bitbake. The downloading of sources and then configuration has to be done by hand. Usually, this is explained in a README. Instead kas is using a project configuration file and does the download and configuration phase. Key features provided by the build tool: - clone and checkout bitbake layers - create default bitbake settings (machine, arch, ...) - launch minimal build environment, reducing risk of host contamination - initiate bitbake build process See the `kas documentation <https://kas.readthedocs.io>`_ for further details. SECURITY NOTICE --------------- At this stage, kas does not validate the integrity of fetched repositories. Make sure to only pull from trusted sources to ensure that the selected revisions are the expected ones, specifically when using mirrors. Later versions of kas may introduce integrity validation mechanisms such as cryptographic checksums to strengthen supply chain security.