Repository navigation
|
I noticed ATHA offers both --plan and --dry-run flags when installing or updating packages. When should I use --plan versus --dry-run during daily package operations? |
Answered by
Bangkah
Jul 21, 2026
Replies: 1 comment
|
Both modes help prevent accidental system breakage, but they serve different purposes in the workflow: --plan (Decision Context): Analyzes and displays where the package is coming from (Official Repo vs. AUR), its dependency impact, and transaction intent before making decisions. --dry-run (Execution Simulation): Simulates the actual command execution without writing or modifying files on your system. Recommended Workflow: |
0 replies
Answer selected by
Bangkah
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Both modes help prevent accidental system breakage, but they serve different purposes in the workflow:
--plan (Decision Context): Analyzes and displays where the package is coming from (Official Repo vs. AUR), its dependency impact, and transaction intent before making decisions.
--dry-run (Execution Simulation): Simulates the actual command execution without writing or modifying files on your system.
Recommended Workflow:
Use --plan first to review source & dependencies, then use --dry-run if you want a non-destructive dry run before running the final execution!