Pacaur is an AUR helper that uses cower as its back-end. It's aimed at advanced users who want to automate repetitive tasks.
Ranked in these QuestionsQuestion Ranking
Pro Minimizes user prompts
Pacaur will ask the user once whether install/updating the desired package(s) is really intended and if so the user has the choice to review the PKGBUILD(s) and .install file(s). Once this is done there is no need for further user intervention.
Pro Uses the same syntax as pacman
Pacaur is a pacman wrapper which adds seamless support to the AUR. Pacman operations are extended to include the AUR without extra work for the user or additional flags to pass.
Pro Same great search as cower
As pacaur is built on top of cower, it has the same very powerful search functionality.
Though since pulling the PKGBUILD and the install files from the AUR server is done by pacaur itself, it is still able to perform a small set of actions if cower fails. (This case is important on an pacman database update which requieres cower to be recompiled. Since pacaur is able to fetch and rebuild cower without using cower, it is quite easy to do so.)
Pro Allows you to use completely separate commands for the AUR
--repo option pacaur does not fall back to the AUR. Vice versa the
--aur option limits pacaur' s actions to the AUR.
Pro Adds seamless access to the AUR
The program falls back to the AUR if the action could not be executed using the official repo. Therefore the user is made aware of the use of the AUR but is not hindered by it not being official.
Pro Colored output
Pacaur extends the colored output to actions not done by pacman or makepkg.
Pro Git Clone
Since the git repo of the AUR package is cloned with a depth of one it does not significantly increase the bandwidth use but has the advantage of being able to calculating the difference between different versions of the PKGBUILD.