User:Svito/AUR helpers

From ArchWiki
< User:Svito
Revision as of 18:12, 24 August 2018 by Spyhawk (talk | contribs) (sign)
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 Specificity
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
repoctlAUR Go Yes Yes No zsh local repository support
aurelAUR (discontinued) Emacs Lisp Yes No 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 Specificity
aurutilsAUR Bash/C Yes Yes Yes Yes Yes Yes Yes 1 zsh vifm, local repository, package signing, clean chroot support, sort by votes/popularity
bauerbillAUR Python Yes Yes Yes Yes Yes Yes No 1 bash, zsh trust management, ABS support, extends powerpill, bb-wrapper for pacman wrapping
PKGBUILDerAUR Python Optional Yes Yes Yes Partial Yes No 1* automatic builds by default, use -F to disable; multilingual, pb-wrapper for pacman wrapping
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 (discontinued) Bash Yes Yes No No No No No
burgaurAUR (discontinued) Python/C Optional Yes No No No No No wrapper for cower

pacman wrappers

  • pacman wrappers may use unsafe flags, in particular for installation of packages from the official repositories and that may lead to a broken system.
  • Unlike pacman(8), these tools are not subject to core strict quality requirements, and may at any point add unsafe flags or break the system in other ways.
Name Written in File review Unsafe flags Clean build Reliable parser Reliable solver Split packages Git clone Diff view Batch interaction Shell completion Specificity
yayAUR Go Yes -Sy*--ask* Yes Yes Yes Yes Yes Yes 1, 2*, 3* bash, fish, zsh fetch PGP keys, sort by votes/popularity, prompt architecture
pakkuAUR Nim Yes -Sy Yes Yes Yes Yes Yes Yes 1 bash, zsh ABS support, AUR comments, fetch PGP keys
pikaurAUR Python Yes -Sy 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 -Ud* Yes Yes Yes Partial Yes Yes 1* bash, zsh, fish automatic builds by default, use -G to disable; AUR comments
auraAUR Haskell Optional Yes Yes No No No Partial 1* bash, zsh automatic builds by default, use --dryrun to disable; downgrade support, multilingual
yaourtAUR Bash/C No [1] [2] -Sy No No No No Optional Optional 2 bash, zsh, fish db backup – not a replacement for system backup! ABS support, print AUR comments, multilingual
aurmanAUR (private) Python Yes -Sy*
Yes Yes Yes Yes Yes Yes 1, 2*, 3* bash, fish fetch PGP keys, sort by votes/popularity, print news
pacaurAUR (discontinued) Bash/C Yes -Ud, --ask Yes Yes Yes Yes Yes Yes 1, 3 bash, zsh multilingual, sort by votes/popularity
wrapaurAUR (discontinued) Bash Yes Yes No No No Yes No mirror updates, print news and AUR comments
packer-aurAUR (discontinued) Bash No Yes No No No No No

Tango-go-next.pngThis article or section is a candidate for moving to User talk:Svito/AUR helpers.Tango-go-next.png

Notes: These comment threads are getting out of hand. (Discuss in User talk:Svito/AUR helpers#)
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)
I'd still use a better indicator for discontinued projects (extra column, or bold 'discontinued' text? Strikethrough on the package name works great too). -- Spyhawk (talk) 08:02, 23 August 2018 (UTC)
The bold discontinued/private looks good to me. -- Alad (talk) 15:26, 23 August 2018 (UTC)
From #archlinux: aurman is not "private" in the sense that the source code is still available to anyone. -- Alad (talk) 17:40, 24 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)
It should be clear enough if done like in AUR helpers#Graphical. -- Alad (talk) 15:29, 23 August 2018 (UTC)
I think doing it that way would be less clear and just unnecessary visual complication, if we have 12 columns, we can just as well have 13. --Larivact (talk) 15:36, 23 August 2018 (UTC)
In that case we should find a better name than "Bad wrap"... -- Alad (talk) 16:35, 23 August 2018 (UTC)
Dangerous splitting? --Larivact (talk) 16:42, 23 August 2018 (UTC)
Well, that doesn't handle the installation/other case (like -Ud for pacaur)... -- Alad (talk) 16:50, 23 August 2018 (UTC)
Unsafe practices? --Larivact (talk) 16:57, 23 August 2018 (UTC)
Unsafe flags is fine to me. Though uses may now be redundant, and we can just list the flags directly. -- Alad (talk) 07:19, 24 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)
Comment: Not sure if "such usage" in the warning is clear enough. It could mean "usage of pacman wrappers in general" or "use of pacman wrappers for packages in the official repositories. Note that latter does not handle the common case of AUR packages with repo dependencies - the installation of said deps will also be wrapped. If nobody has arguments against I'd thus go with an explicit "usage of pacman wrappers".

Some reference to the "Bad wrap" (or whatever column name we decide on) could also be made. -- Alad (talk) 16:38, 23 August 2018 (UTC)

This opens another can of worms: some helpers are optionally pacman wrappers, like bauerbill and pkgbuilder which include separate programs for this functionality. I'm not sure they'd fit under "AUR only" though. -- Alad (talk) 16:58, 23 August 2018 (UTC)
Or perhaps not, since "bad wrap" is only relevant if it does so by default. -- Alad (talk) 17:10, 23 August 2018 (UTC)
I don't feel "by default" is presented in an explicit manner, especially in regards to the wrappers that don't use bad wraps even as option. Maybe use something like "not by default" where relevant instead? Or an asterisk with the "*not be default" below the table? -- Spyhawk (talk) 09:50, 24 August 2018 (UTC)
I guess this is covered by "Optional" now. -- Alad (talk) 16:22, 24 August 2018 (UTC)
Comment: I'd set the "Bad wrap" column right of "File review", since latter is more important in terms of safety (besides looking somewhat neater with other tables starting in "File review" as well). -- Alad (talk) 16:49, 23 August 2018 (UTC)
This is what it looks like: [3] -- Alad (talk) 17:23, 23 August 2018 (UTC)
I'm no longer convinced this actually looks better though. More opinions? -- Alad (talk) 17:36, 24 August 2018 (UTC)
The potentially unsafe flag column is closely related to Batch interaction. Maybe move it to the end instead? In the end, it doesn't matter which order it is displayed. Also, to keep it simple, yellow color could be used for optional flags, red for enabled by default, green for no unsafe flag at all. -- Spyhawk (talk) 18:12, 24 August 2018 (UTC)