Pionux OS Package Manager

There's a point in everyone's life when you feel the need to write an AUR helper because there are only about 20 of them. So say hi to 20+1.

pi is based on the design of yaourt, apacman and pacaur. It is developed with these objectives in mind:

• Provide an interface for pacman
• Yaourt-style interactive search/install
• Minimal dependencies
• Minimize user input
• Know when git packages are due for upgrades

• Perform advanced dependency solving
• Download PKGBUILDs from ABS or AUR
• Tab-complete the AUR
• Query user up-front for all input (prior to starting builds)
• Narrow search terms (pi linux header will first search linux and then narrow on header)
• Find matching package providers during search and allow selection
• Remove make dependencies at the end of the build process
• Run without sourcing PKGBUILD

If you are migrating from another AUR helper, you can simply install pi with that helper.

Alternatively, the initial installation of pi can be done by cloning the PKGBUILD and building with makepkg:

git clone https://aur.archlinux.org/pi.git
cd pi
makepkg -si

All support related to pi should be requested via GitHub issues. Since pi is not officially supported by Arch Linux, support should not be sought out on the forums, AUR comments or other official channels.

A broken AUR package should be reported as a comment on the package's AUR page. A package may only be considered broken if it fails to build with makepkg. Reports should be made using makepkg and include the full output as well as any other relevant information. Never make reports using pi or any other external tools.

Make sure you have the Color option in your /etc/pacman.conf (see issue #123).

The default behavior was changed after v8.918 (see 3bdb534 and issue #554). To restore the package-skip behavior use --combinedupgrade (make it permanent by appending --save). Note: skipping packages will leave your system in a partially-upgraded state.

pi uses git diff to display diffs, which by default tells less not to page if the output can fit into one terminal length. This behavior can be overridden by exporting your own flags (export LESS=SRX).

pi --editmenu --nodiffmenu --save

pi -{OPERATION} --aur pi -{OPERATION} --repo

This message does not mean that updated AUR packages are available. It means the packages have been flagged out of date on the AUR, but their maintainers have not yet updated the PKGBUILDs (see outdated AUR packages).

pi resolves all dependencies ahead of time. You are free to edit the PKGBUILD in any way, but any problems you cause are your own and should not be reported unless they can be reproduced with the original PKGBUILD.

pi uses an hash cache for development packages. Normally it is updated at the end of the package install with the message Found git repo. If you transition between aur helpers and did not install the devel package using pi at some point, it is possible it never got added to the cache. pi -Y --gendb will fix the current version of every devel package and start checking from there.

Check CONTRIBUTING.md for more information.