Arch Linux User Repository

[2017-12-15] This project is now unmaintained. Users are encouraged to move to another solution (see wiki for alternatives).

Please quote the $pkgdir.

This is correct. This latest update contains all the changes done between July 2017 and December 2017, as well as a few changes done after the development stopped - a few regression fixes, one additional minor bug fix, and the inclusion of fixes people sent me or made in their own fork.

The release number chosen (4.7.90) reflects that this release is about 90% of what I initially planned for the 4.8 release.

@virtualdemon: No, Spyhawk always said that there would be a final release with the remaining already merged commits when pacman 5.1 would land, and that’s what happened. The development is still stopped, and the GitHub repo is even read-only now.

Last Updated: 2018-05-30 14:21 ! Will the development of this package continue?

Honestly I've been looking at different ones, and the closest I've found to the same functionality in the same way as pacaur (aurman) is super super slow in comparison, doesn't support searching (even refusing to search with pacman and say that the aur can't be searched with it right now), and several other minor, but adding up to really annoying issues. Idk, maybe my expectations are too much or maybe I've just been spoiled by pacaur

Maybe just switch to a maintained version before waiting for this to break.

I'm getting "/usr/bin/pacman: unrecognized option: --color never". Is this somewhere in my config or in pacaur? I don't have any ~/.config/pacaur, but I don't know if there's a global file I might need to modify.

@neitsab and others: Thank you for your kind words. Note I'll push a few additional regression fixes when pacman 5.1 is released. The big impact on server log of cower has also been fixed a few weeks ago, so I'll not bother finishing the work to make pacaur use auracle instead.

Oh my, I just discovered at the turn of a wiki page that pacaur went unmaintained. I've read through your posts and understand why you'd want to close this chapter. It makes sense, you should never have to degrade your quality of life for such things.

It's long past after the events, but I still want to express my gratitude for the demanding and undeserving work that went into pacaur. I've been using it since my very beginnings in Arch-land, after I got horrified with my first "yaourt" invocation and looked for an alternative that would follow a much more KISS approach. pacaur has served its role efficiently and diligently ever since, and went to constitute a core part of my workflow for many years.

Thank you Spyhawk, and farewell to pacaur.

As I understand it, Pacaur itself is Bash, just "built upon the well designed cower and expac C backends". Design decisions ended up being the problem (cower was redone to auracle), but neither are his projects, so I guess it was the Bash code: https://github.com/rmarquis/pacaur -> description link

Aurman = Python, Yay = Go and Trizen = Perl, so people probably just wanna have fun trying out different things: https://github.com/polygamma/aurman, https://github.com/Jguer/yay, https://github.com/trizen/trizen (click the line just below the "commits", "branches", etc. for languages used)