# west mit Homebrew, apt installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für west in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:west ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install west ``` Evidenz: local Homebrew formula metadata ### Linux - Debian apt (92%): ```sh sudo apt install west ``` Evidenz: Debian stable package indexes: west from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz ## Paketfakten - **Paketschlüssel:** brew:west - **Paketmanager:** Homebrew - **Paketmanager-Seite:** - **Version:** 1.5.0 - **Quellzusammenfassung:** Zephyr meta-tool - **Homepage:** - **Repository:** - **Lizenz:** Apache-2.0 - **Quellarchiv:** - **Generiert:** 2026-08-04T22:13:35+00:00 ## Executables - west (cli) - west (Alias) ## Abhängigkeiten - libyaml - python@3.14 ## Installationsverhalten - Post-install-Hook: nicht definiert - Bottle: verfügbar auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Version und Aktualität - Seite generiert: 2026-08-04 - Manager-Version: 1.5.0 - lokale Daten: OK - Upstream-Repository: https://github.com/zephyrproject-rtos/west - Info: No package-manager update timestamp was available. - Info: No cached GitHub release or tag data was available. ## Projektgeschichte und Nutzung west is Zephyr's meta-tool: a Python CLI for managing Zephyr workspaces, multiple Git repositories, manifests, and common build, flash, debug, and extension workflows. The Zephyr documentation calls it a swiss-army-knife command line tool developed in its own repository. ### Projektgeschichte west was added because Zephyr needed two things at once: a standardized way to work with multiple Git repositories and an extensible command-line interface for basic Zephyr workflows. Zephyr's own history-and-motivation page explains that existing tools such as Git submodules and Google's Repo were examined but did not satisfy the project's requirements, including downstream overrides, Windows support, and commit-based or continuous project updating. The GitHub repository was created in May 2018, and Zephyr 1.14-era release material introduced west for multiple-repository management plus improved flashing and debugging. That timing matches Zephyr's transition from a single RTOS repository mindset toward a modular embedded ecosystem with external modules, HALs, tools, samples, and downstream distributions. west evolved through a pre-1.0 period where the tool's packaging and manifest APIs were still settling. Its v0.6 line removed the old split bootstrapper model and made core commands part of the PyPI-distributed package. West v1.0.0, published in February 2023, declared the APIs stable and dropped the compatibility modules needed by the old Zephyr 1.14 LTS line. ### Adoptionsgeschichte west adoption is tied directly to Zephyr adoption: most Zephyr users encounter it during workspace setup. The standard flow is `west init` to create a workspace and clone the manifest repository, followed by `west update` to fetch the projects named in the manifest. Vendors and downstreams also use west manifests to pin Zephyr and module revisions for reproducible embedded products. Because Zephyr is not just a kernel tree but a collection of code, modules, vendor HALs, and tools, west became the package-nerd-visible front door for many embedded developers. It is also extensible, so Zephyr can expose workflow commands such as build, flash, debug, and signing through the same top-level CLI. ### Wie es verwendet wird west workspaces contain a `.west` directory, a manifest repository, and multiple project repositories defined in a YAML manifest, usually `west.yml`. The command's core model is deterministic: the manifest repository's commits name exact or trackable revisions in project repositories, and `west update` makes the workspace match that manifest. Typical users run `west init -m` with a Zephyr or downstream manifest, `west update` to clone modules, and Zephyr extension commands such as `west build`, `west flash`, or `west debug` during firmware work. Advanced users use `west manifest`, `west list`, `west forall`, `west compare`, and newer commands such as `west grep` to inspect or operate across a multi-repository workspace. ### Warum Paket-Nerds sich dafür interessieren west is significant because it packages Zephyr's multi-repository source distribution into a single command-line mental model. For embedded developers, installing `west` is often the step that turns a pile of Git repositories into a coherent Zephyr SDK-style workspace. ### Zeitleiste - May 2018: zephyrproject-rtos/west repository is created. - Zephyr 1.14 era: west is introduced for multiple repository management and enhanced flashing/debugging workflows. - v0.6.x: west moves away from a split bootstrapper model and is distributed as one PyPI package. - February 20, 2023: west v1.0.0 is published with stable APIs and no Zephyr 1.14 LTS compatibility modules. - 2023-2025: later releases add workspace comparison, grep, aliases, manifest filtering, packaging updates, and auto-caching support. ### Quellen - - - - - - - - ## Sicherheitshinweise narrow executable package without higher-risk signals. - **Geiger-Risiko:** grün / niedrig - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Linux: /etc/westconfig, ~/.westconfig, $XDG_CONFIG_HOME/west/config, /.west/config - macOS: /usr/local/etc/westconfig, ~/.westconfig, /.west/config - Windows: %PROGRAMDATA%\west\config, %USERPROFILE%\.westconfig, \.west\config ## Details aus der Quelldatenbank - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** west - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Andere Paketmanager-Einträge - Debian apt - west - 1.3.0-3: normalized package name match | Debian stable package indexes: west from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Zephyr RTOS Project meta-tool | https://github.com/zephyrproject-rtos/west ## Verwandte Links - [Source-control packages](https://pkg.so/de/source-control-tools/) - Belongs to a source-control command family. - [Terminal utility packages](https://pkg.so/de/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://pkg.so/de/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://pkg.so/de/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [python@3.14](https://pkg.so/de/brew/python-3-14/) - Runtime dependency declared by Homebrew. - [dtc](https://pkg.so/de/brew/dtc/) - Shares pkgdb curated category or tags: cli, developer-tools, embedded. - [arduino-cli](https://pkg.so/de/brew/arduino-cli/) - Shares pkgdb curated category or tags: cli, developer-tools, embedded. - [platformio](https://pkg.so/de/brew/platformio/) - Shares pkgdb curated category or tags: cli, developer-tools, embedded. - [arm-none-eabi-gcc](https://pkg.so/de/brew/arm-none-eabi-gcc/) - Shares pkgdb curated category or tags: cli, developer-tools, embedded. - [open-ocd](https://pkg.so/de/brew/open-ocd/) - Shares pkgdb curated category or tags: cli, developer-tools, embedded. - [arm-none-eabi-binutils](https://pkg.so/de/brew/arm-none-eabi-binutils/) - Shares pkgdb curated category or tags: cli, developer-tools, embedded. - [arm-none-eabi-gdb](https://pkg.so/de/brew/arm-none-eabi-gdb/) - Shares pkgdb curated category or tags: cli, developer-tools, embedded. - [stlink](https://pkg.so/de/brew/stlink/) - Shares pkgdb curated category or tags: cli, developer-tools, embedded. - [charm-tools](https://pkg.so/de/brew/charm-tools/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, developer, developer-tools, libyaml, python. - [cobo-cli](https://pkg.so/de/brew/cobo-cli/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, developer, developer-tools, libyaml, python. - [cookiecutter](https://pkg.so/de/brew/cookiecutter/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, developer, developer-tools, libyaml, python. ## Combined YAML source View the package source record on GitHub. [combined/west.yml](https://github.com/mxcl/pkgdb/blob/main/combined/west.yml) ## Quellen - pkg.so package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - pkgdb category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph