Hey guys! I'm the lead developer of raur. I was simply wondering if it could be added to the bottom. It seems to be more comprehensive than the existing aur.rs as it implements the entire interface, as well as all search strategies provided by the interface.
- I'm hesitant in adding a second project to the page which has no AUR package, but I guess it's part of the "bundle everything" philosophy of these languages... -- Alad (talk) 19:00, 18 May 2019 (UTC)
Special:Diff/573543/573551: Good revert, I did these late into sleepless night and did not notice this were huge and not that thought through changes :/
Merge note definitions for partial and optional as part of legends list?This was a mistake, note there exactly makes sense according to style rules.
- Add known used unsafe flags to legend, add that asterisk means optional, as it may be unclear?
- Move legend concerning pacman wrappers only inside its section? Alternatively mention these apply only to pacman wrappers, example text:
- Unsafe flags
- Potentially harmful pacman flags that could be used by #pacman wrappers.
- Note: Asterisk means these pacman flags are optionally enabled.
- Batch interaction
- Ability of #pacman wrappers to prompt before the build process and package transactions, in particular:
- Combined summary of repository and AUR package upgrades;
- Resolution of package conflicts and choice of providers.
- Batch interaction isn't specific to pacman wrappers, at least not 2. The legend denotes it as a column though, which it isn't. At the same time, I'm not sure if replacing "columns" with "columns and values" is a good idea.
- If we document all the unsafe flags, I would argue it's out of scope in this article and should be expanded in System_maintenance#Avoid_certain_pacman_commands instead. (Side-note: what if a regular AUR helper uses an unsafe command to e.g. install dependencies? None of the current entries do, but it's a possible scenario.) -- Alad (talk) 13:26, 25 May 2019 (UTC)
- How about expanding the note:
- Optional means that a feature is available, but only through a command-line argument or configuration option. Partial means that a feature is not fully implemented, or that it partially deviates from the given criteria.
- Batch interaction indicates the ability to prompt before the build process and package transactions. In particular:
- 1. Combined summary of repository and AUR package upgrades;
- 2. Resolution of package conflicts and choice of providers.
- I've looked at System_maintenance#Avoid_certain_pacman_commands again and it contains all needed detail already, apart from the --ask option which is niche (and linked from in the table where appropriate). -- Alad (talk) 22:02, 25 July 2019 (UTC)
Add yup to Pacman wrappers
Links: github AUR
Right now yup ticks every box in the 'Pacman Wrappers' table except for 'Split packages'. It has code completion working mostly in zsh and will soon support bash and fish too.
It fetches pgp keys for you. It shows the PKGBUILD before installing by default for security reasons. It shows far more relevant search results that other AUR helpers on the market.
- It's another yaourt clone - pretty sure we have enough of those in the table already. -- Alad (talk) 20:11, 21 July 2019 (UTC)
- I would argue the splitting into "packages" is the main distinguish feature - things like an ncurses interface are superficial in my book.
- Generally speaking, most AUR helpers have turned out to be either vaporware or small variations on existing work. Some recent examples: Alad (talk) 21:56, 25 July 2019 (UTC) AUR, AUR, AUR, AUR, AUR, AUR, AUR. So let's wait a bit how this projects evolves before adding it to the wiki. --