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)