Kama usage — Keru OS

Kama's commands are few on purpose. Here's the complete set:

Command	What it does
`kama fetch <pkg>`	Download and extract source for a package into the cache.
`kama build <pkg>`	Stage-build one package (configure/make) into its stage dir.
`kama install <pkg>`	Build + install a package into `$ROOT` (staging-aware).
`kama make <pkg>`	High-level: fetch deps, build, install, then purge temp deps.
`kama purge [pkg ...]`	Remove temp build-time deps after a successful install.
`kama info <pkg>`	Show a recipe's metadata (name, version, url, deps).
`kama help`	Print the command reference.

Making a package, end to end

kama make is the command that ties it together. For a package with dependencies it walks through:

$ kama make firefox

[ kama ] building temp deps for firefox: rust gtk3
  ... fetch, build, install each temp dep ...
[ kama ] building firefox
  ... stage build + install into $ROOT ...
[ kama ] purging temp deps for firefox: rust gtk3

Environment & config

Kama reads a few things to know where to work:

Variable	Default
`PKGDIR`	The recipe repo (kama-packages, sibling by default).
`MAKE_CONF`	`/etc/kama/make.conf` — profile settings, if present.
`ROOT`	`/tmp/keru/root` — where installed files go.
`CACHEDIR`	`/var/cache/kama` — source, download, and stage dirs.
`PURGE_TEMP_DEPS`	`1` — whether temp deps are purged after building.

Fetch details

Mirror first. Downloads try SOURCE_MIRROR before upstream, so the org mirror (e.g. mirror.keru.org) can carry the load.
Cached. Already-downloaded source is reused; already-extracted source isn't re-extracted.
Auto-extract. Tar (gz/xz/bz2/plain) and zip are handled automatically by extension.

Kama's surface stays tiny because the complexity lives in recipes, not the manager. Read how recipes work next.

← Kama overview