Manjaro Linux Provisioning

Standards and best practices for creating provisioning scripts for Manjaro Linux environments. Emphasizes idempotency, clean user interaction via Gum, and consistent package management.

Environment Requirements

This skill is designed for provisioning scripts targeting **Manjaro Linux** systems:

User Input Handling

All user interaction should use the **Gum** package for consistent, beautiful CLI prompts:

**Example:**

```bash

Choice menu

SELECTED=$(gum choose "Option 1" "Option 2" "Option 3")

Yes/no confirmation

if gum confirm "Proceed with installation?"; then

# proceed

fi

Text input

USERNAME=$(gum input --placeholder "Enter username")

Multi-line input

CONFIG=$(gum write --placeholder "Paste config here...")

```

Refer to [Gum documentation](https://github.com/charmbracelet/gum) for full API.

Script Design Principles

Idempotency

All scripts must be **re-runnable** without causing errors or unintended side effects:

Minimal Comments

Do **not** add unnecessary comments. Only comment when:

**Bad:**

```bash

Install git

yay -S git --noconfirm

```

**Good:**

```bash

Only needed if using custom PGP keyring

yay -S git --noconfirm

```

Package Management

pacman (Official Repositories)

Use `pacman` for packages from official Manjaro/Arch repos:

```bash

pacman -S <package> --noconfirm --noprogressbar --quiet

```

yay (AUR Packages)

Use `yay` for packages from the Arch User Repository:

```bash

yay -S <package> --noconfirm --noprogressbar --quiet

```

Standard Flags

Always include these flags for non-interactive, clean output:

curl Commands

Add `-s` (silent mode) to all `curl` commands:

```bash

curl -s https://example.com/install.sh | bash

```

Error Handling

Include robust error handling in all scripts:

Exit on Error

Use `set -e` at the beginning of every script to exit immediately on any command failure:

```bash

#!/usr/bin/env zsh

set -e

rest of script

```

Additional Safety Options (Optional)

For stricter error handling, consider:

```bash

set -euo pipefail

```

Logging

Use a **consistent logging function** for status messages:

```bash

status() {

echo "[INFO] $1"

}

status "Installing packages..."

yay -S neovim --noconfirm --noprogressbar --quiet

status "Installation complete"

```

Standardize the `status` function across all scripts for uniform output.

Example Script Template

```bash

#!/usr/bin/env zsh

set -e

status() {

echo "[INFO] $1"

}

status "Starting provisioning..."

Check if already installed

if ! command -v neovim &> /dev/null; then

status "Installing Neovim..."

yay -S neovim --noconfirm --noprogressbar --quiet

else

status "Neovim already installed, skipping"

fi

User confirmation

if gum confirm "Configure dotfiles?"; then

status "Configuring dotfiles..."

# configuration logic here

fi

status "Provisioning complete"

```

Key Constraints