-
Notifications
You must be signed in to change notification settings - Fork 0
Commands
Muhammad Dhiyaul Atha edited this page Apr 1, 2026
·
4 revisions
atha install [--dry-run] [--plan] [--yes] <pkg> [pkg2 ...]Installs one or more packages. ATHA evaluates official repositories first and falls back to AUR when needed.
-
--planperforms decision analysis: what will be installed, from where, and why. -
--dry-runperforms execution simulation: which commands would run, without applying changes.
atha remove [--dry-run|--plan] [--yes] <pkg> [pkg2 ...]Removes one or more installed packages.
-
--planexplains removal decisions and expected impact. -
--dry-runpreviews remove commands and skips non-installed targets.
atha search <keyword>Searches packages by keyword using pacman.
atha update [--dry-run|--plan]Runs a full system upgrade via pacman.
-
--planshows update availability and reasoning-oriented summary. -
--dry-runpreviews update commands without modifying the system.
atha list [installed|all]Shows installed packages or a limited list of all available packages.
atha info <pkg>Displays package metadata from repositories.
atha doctorChecks required dependencies and returns non-zero exit code when required tools are missing.
Doctor also checks runtime readiness:
- pacman lock state
- writable cache/state paths
- DNS reachability for archlinux.org and aur.archlinux.org
atha history [--limit N] [--full|--timeline|--summary] [--action <name>] [--status <name>]Shows recent ATHA operations from local history state.
-
--timelineprints concise chronological events. -
--summaryprints counts by action and status. -
--actionfilters events by action (install,remove,update). -
--statusfilters events by status (success,failed,planned,cancelled,skipped).
- Commands that modify system packages may require sudo privileges.
- AUR operations require build tooling such as
gitandmakepkg. - Use
--planwhen you want analysis and decision context. - Use
--dry-runwhen you want execution preview only.