Requirements

DPM is a self-contained binary. You only need a supported OS and a shell.

Runtime requirements

To run dpm and dpm-tui:

Linux or macOS (see platform table below)
A POSIX-compatible shell (sh, bash, zsh)
curl is required for the install script and community profile fetches

Go and Rust are not required on the target machine. The binaries are statically compiled and ship with everything they need.

Supported platforms

        Linux   x86_64    ✓  fully supported
        Linux   arm64     ✓  fully supported
        macOS   x86_64    ✓  fully supported
        macOS   arm64     ✓  fully supported (Apple Silicon)
        Windows            ✗  not supported
      

Linux distributions

Any Linux distribution is supported as a host. The available install methods for individual tools depend on what package managers are present:

Debian / Ubuntu / Kali, apt is available and usually gives the widest coverage
Arch Linux, no apt, so tools fall back to pip, cargo, or direct HTTP
Fedora / RHEL, no apt, so fallback behavior is similar to Arch
Any distro with Homebrew, brew methods become available

If a tool's preferred install method isn't available on your system, DPM tries the next defined method automatically. See Install Methods for how fallback works.

TUI requirements

The TUI has one additional requirement beyond the CLI:

dpm must be in PATH because dpm-tui starts dpm serve --stdio on launch.
A terminal with 256-colour support for full theme rendering. Most modern terminal emulators qualify.
Minimum terminal width of ~80 columns for the three-column docs layout to render correctly. Below ~720px equivalent, the sidebar hides automatically.

Package manager requirements per method

        apt      apt-get in PATH, sudo available
        brew     Homebrew installed, brew in PATH
        pip      python3 and pip3 in PATH
        cargo    Rust toolchain installed, cargo in PATH
        http     curl in PATH, write access to ~/.dpm/
      

DPM does not install package managers for you. If none of the methods for a given tool are available, the install fails with a message listing what was tried.

Disk and PATH

The install script places dpm and dpm-tui in ~/.local/bin/. DPM-managed state lives under ~/.dpm/, and managed tool links are exposed from ~/.dpm/bin/.

Run dpm doctor at any time to check PATH setup, DPM root directory, and tool accessibility.

← CLI Reference