zara/zephyr - zephyr - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Pieter De Gendt	4c5e74deae	scripts: west_commands: patch: Use subprocess cwd Instead of changing directories, pass the cwd argument to the different subprocess calls. Signed-off-by: Pieter De Gendt <pieter.degendt@basalte.be>	6 months ago
Pieter De Gendt	78f96a6aba	scripts: west_commands: Add module filter argument to patch command Allow to run the west patch extension for specific modules only. Signed-off-by: Pieter De Gendt <pieter.degendt@basalte.be>	6 months ago
Gerhard Jörges	e4b2fe4b78	scripts: west_commands: fix type of path options Using `west patch` with the `--patch-base`, `--patch-yaml` or `--west-workspace` option results in an unhandled AttributeError in filter_args() because the function expects these args to be of type path. Adding the type to the argument definition forces argparse to create variables of type path. Signed-off-by: Gerhard Jörges <joerges@metratec.com>	6 months ago
Chris Friedt	ad611395ee	scripts: west_commands: add the west patch command In smaller projects and organizations, forking Zephyr is usually a tenable solution for development continuity, in the case that bug-fixes or enhancements need to be applied to Zephyr to unblock development. In larger organizations, perhaps in the absence of healthy patch management, technical debt management, and open-source policies, forking and in-tree changes can quickly get out of hand. In other organizations, it may simply be preferable to have a zero-forking / upstream-first policy. Regardless of the reason, this change adds a `west patch` command that enables users to manage patches locally in their modules, under version control, with complete transparence. The format of the YAML file (detailed in a previous comit) includes fields for filename, checksum, author, email, dates, along with pr and issue links. There are fields indicating whether the patch is upstreamble or whether it has been merged upstream already. There is a custom field that is not validated and can be used for any purpose. Workflows can be created to notify maintainers when a merged patch may be discarded after a version or a commit bump. In Zephyr modules, the file resides conventionally under `zephyr/patches.yml`, and patch files reside under `zephyr/patches/`. Sample usage applying patches (the `-v` argument for additional detail): ```shell west -v patch apply reading patch file zephyr/run-tests-with-rtt-console.patch checking patch integrity... OK patching zephyr... OK reading patch file zephyr/twister-rtt-support.patch checking patch integrity... OK patching zephyr... OK reading patch file zephyr/multiple_icntl.patch checking patch integrity... OK patching zephyr... OK reading patch file zephyr/move-bss-to-end.patch checking patch integrity... OK patching zephyr... OK 4 patches applied successfully \o/ ``` Cleaning previously applied patches ```shell west patch clean ``` After manually corrupting a patch file (the `-r` option will automatically roll-back all changes if one patch fails) ```shell west -v patch apply -r reading patch file zephyr/run-tests-with-rtt-console.patch checking patch integrity... OK patching zephyr... OK reading patch file zephyr/twister-rtt-support.patch checking patch integrity... OK patching zephyr... OK reading patch file zephyr/multiple_icntl.patch checking patch integrity... OK patching zephyr... OK reading patch file zephyr/move-bss-to-end.patch checking patch integrity... FAIL ERROR: sha256 mismatch for zephyr/move-bss-to-end.patch: expect: 00e42e5d89f68f8b07e355821cfcf492faa2f96b506bbe87a9b35a823fd719cb actual: b9900e0c9472a0aaae975370b478bb26945c068497fa63ff409b21d677e5b89f Cleaning zephyr FATAL ERROR: failed to apply patch zephyr/move-bss-to-end.patch ``` Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>	7 months ago