User:Svito/AUR helpers

From ArchWiki
< User:Svito
Revision as of 23:40, 22 August 2018 by Svito (talk | contribs) (undo subsections, may be too much detail)
Jump to navigation Jump to search
Comment: This is draft for AUR helpers started from Talk:AUR helpers#Native pacman revisited. Use Template:Comment for suggestions on the draft page.
Maybe a smaller or no fixed width? The GUI table (AUR helpers#Graphical) is not 100% either. -- Alad (talk) 19:58, 21 August 2018 (UTC)
100% agreed ;) Unfixed width for all tables and it looks better on any resolution IMO. -- Svito (talk) 20:56, 21 August 2018 (UTC)

Search and download only

Comment: From User:halosghost: Search/Download-only could be a good section title, because some of these tools support package downloads as well. -- Alad (talk) 21:56, 21 August 2018 (UTC)
Name Written in File review Reliable parser Reliable solver Git clone Shell completion Specifity
pbgetAUR Python Yes Yes Yes
yaahAUR Bash Yes Yes Optional bash
auracle-gitAUR C++ Yes Yes Yes No print build order
cowerAUR C Yes Yes No bash, zsh regex support, sort by votes/popularity
package-queryAUR C Yes No [1]
repoctlAUR Go Yes Yes [2] No zsh local repository support
aurelAUR [3] Emacs Lisp Yes No discontinued; Emacs integration

AUR only

Name Written in File review Clean build Reliable parser Reliable solver Split packages Git clone Diff view Batch interaction Shell completion Specifity
aurutilsAUR Bash/C Yes Yes Yes Yes Yes Yes Yes 1 zsh vifm, local repository, package signing, clean chroot support, sort by votes/popularity
naamanAUR Python Optional Yes Yes Partial Partial Yes No 1* bash automatic builds by default, use --fetch to disable; use -d to enable the solver
repofishAUR Bash Optional Yes No No No Yes Yes 1* automatic builds by default, use check or update to disable; local repository support
aurgetAUR Bash Optional Yes No No No No No bash, zsh sort by votes
spinachAUR [4] Bash Yes Yes No No No No No discontinued
burgaurAUR [5] Python/C Optional Yes No No No No No discontinued; wrapper for cower

Pacman wrappers

When used as replacement for pacman(8) commands such as pacman -Syu, the following are obeyed by default: [6]

  • avoid partial upgrades, for example pacman -Syu is not split to pacman -Sy and pacman -S packages
  • avoid manual database manipulation or usage of libalpm(3) – use pacman directly instead
Warning:
  • Notwithstanding these criteria, AUR helpers may deviate from pacman(8) in various ways, in particular for installation of packages in the official repositories. Such usage is therefore not supported or recommended.
  • Keep in mind that using the same command for official and user-submitted packages blurs the lines between packages that are supported, and packages that might be arbitrary broken things; latter requiring careful attention before installation.
Name Written in Bad wrap File review Clean build Reliable parser Reliable solver Split packages Git clone Diff view Batch interaction Shell completion Specifity
yayAUR Go Yes Yes Yes Yes Yes Yes Yes 1, 2*, 3* bash, fish, zsh fetch PGP keys, sort by votes/popularity, prompt architecture
pakkuAUR Nim splits -Syu Yes Yes Yes Yes Yes Yes Yes 1 bash, zsh ABS support, AUR comments, fetch PGP keys
pikaurAUR Python splits -Syu Yes Yes Yes Yes Yes Yes Yes 1, 2, 3 bash, fish, zsh dynamic users, multilingual, sort by votes/popularity, print news, ignore errors
trizenAUR Perl Yes Yes Yes Yes Partial Yes Yes 1* bash, zsh, fish automatic builds by default, use -G to disable; AUR comments
bauerbillAUR Python Yes Yes Yes Yes Yes Yes No 1 bash, zsh trust management, ABS support, extends powerpill
PKGBUILDerAUR Python Optional Yes Yes Yes Partial Yes No 1* automatic builds by default, use -F to disable; multilingual
auraAUR Haskell Optional Yes Yes No No No Partial 1* bash, zsh automatic builds by default, use --dryrun to disable; downgrade support, multilingual
wrapaurAUR Bash Yes Yes No No No Yes No mirror updates, print news and AUR comments
packer-aur-gitAUR Bash No Yes No No No No No
yaourtAUR Bash/C splits -Syu No [7] [8] No No No No Optional Optional 2 bash, zsh, fish backup, modifies pacman database!; ABS support, print AUR comments, multilingual
aurmanAUR [9] Python Yes Yes Yes Yes Yes Yes Yes 1, 2*, 3* bash, fish closed development; fetch PGP keys, sort by votes/popularity, print news
pacaurAUR [10] Bash/C uses -Ud Yes Yes Yes Yes Yes Yes Yes 1, 3 bash, zsh discontinued; multilingual, sort by votes/popularity
Comment: "Closed development" is more accurate than "Not for public use" in aurman's Notes. Anyone can use aurman by installing the AUR package, they just can't participate in development. -- Alad (talk) 22:11, 21 August 2018 (UTC)
Note that bauerbill fits the criteria of "closed development" too. I'd also suggest keeping pacaur in a separate table, or removing it entirely - unlike the others, it's officially deprecated -- Spyhawk (talk) 19:02, 22 August 2018 (UTC)
I don't like this suggestion, it's overly complex and makes a big deal out of small details.
Also bauerbill isn't "closed" in the sense aurman is, since anyone can leave requests on the bauerbill forum page. -- Alad (talk) 22:05, 22 August 2018 (UTC)
Just to be clear do you think so of Special:Diff/536803/next as well or only of Spyhawk suggestion?
I checked recent Xyne posts and homepage myself and he accepts suggestions via email and forum so I did not move it. -- Svito (talk) 22:36, 22 August 2018 (UTC)
Comment: I think using a separate section for pacman wrappers deals with the problematic perfectly. However, I'm unsure if issues should be included in the Specificity column (as done for yaourt below; splits -Syu is missing for some entries). The column is to the far right of the table and may be overlooked. That said, a second column might be overkill. I wonder what incorporating remarks on pacman wrapping in the Name column would look like. Alad (talk) 19:53, 21 August 2018 (UTC)
Changed Specifity to Notes, added split pacman -Syu and colored helper column accordingly. Thanks for all feedback! -- Svito (talk) 21:06, 21 August 2018 (UTC)
I think the colored table headers are confusing because it's not obvious what the colors mean. I'd prefer a dedicated column. --Larivact (talk) 04:22, 22 August 2018 (UTC)
The warning on pacman wrappers could probably be included here, instead of the criteria. -- Alad (talk) 19:54, 21 August 2018 (UTC)