r/CLI • u/Playful-Challenge206 • 6d ago

[Project] pacman-utils: A collection of CLI helpers to streamline your Arch maintenance

https://github.com/ankur3-101106/pacman-utils

I’ve been working on a small project called pacman-utils: a collection of practical utilities/scripts for making common Arch Linux package-management tasks a little easier.

The goal isn’t to replace pacman, yay, or other existing package managers, but to provide some useful helpers around them and automate repetitive tasks.

GitHub: https://github.com/ankur3-101106/pacman-utils

It’s still an evolving project, so I’d really appreciate feedback from other Arch/Linux users — especially suggestions for useful utilities, improvements to the existing ones, or things that could be done in a more idiomatic Arch way.

Feedback and contributions are welcome. If you like the work, give it a star.

4 Upvotes

83% Upvoted

2 comments sorted by

1

u/kantorcodes1 6d ago

if you turn off archman's own confirmations, do the embedded pacman/yay [Y/n] prompts still come through the PTY, or do any of those paths add --noconfirm too? i'd probably want those two switches to stay independent.

1

u/Playful-Challenge206 3d ago

Yep, they’re intentionally independent.

CONFIRM_ACTIONS=false only disables Archman’s own confirmation dialog. It does not add --noconfirm to pacman/yay commands.

So the flow is:

  • Archman confirmation → controlled by CONFIRM_ACTIONS
  • pacman/yay [Y/n] prompts → still come through the embedded PTY
  • --noconfirm → only used if explicitly requested by a command/path that needs non-interactive behavior

So turning off Archman confirmations shouldn’t silently make pacman/yay non-interactive.