-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
If you only ever use a single operating system, you probably should! However, if you frequently switch between Debian servers, Arch desktops, macOS workstations, and Termux on your phone, pkgwrap eliminates context-switching friction by giving you one muscle-memory command to use everywhere.
No, it does not. pkgwrap is purely a lightweight CLI wrapper that translates your unified command into native syntax and passes it down to the underlying package manager (like apt, dnf, or pacman). Your system's package database and native tools remain completely untouched.
Yes. By default, pkgwrap does not run as root; instead, it detects if an operation requires root privileges and prompts you for confirmation before prepending sudo to the underlying command. It uses safe subprocess execution without shell injection vulnerabilities, so your system's standard security policies still apply.
The base name pkgwrap was unavailable in the global Python Package Index (PyPI) namespace. We appended a unique identifier to ensure smooth publishing and installation, but the actual CLI command you use in your terminal remains simply pkgwrap (or the short alias pkw).
Absolutely. pkgwrap is highly effective for writing universal setup scripts, especially if you juggle containers based on different distributions like Alpine (apk) or Ubuntu (apt). Just remember to use the -y flag to ensure the process doesn't hang waiting for interactive user input.
Yes, it is built with automation in mind. You can append the -y or --yes flag to bypass pkgwrap's internal sudo confirmations as well as the native package manager's prompts. This makes it perfect for writing cross-platform dotfile bootstrappers.
The execution will safely halt and raise a BackendNotFoundError, printing a clear message that no supported package manager could be found on the system. If you are using a lesser-known OS, we highly encourage you to open a PR to add a backend for it!
Not at this time. Windows package managers like winget and choco have paradigms and permission models that differ significantly from Unix-like environments. However, native Windows support is officially on our project roadmap for a future release.