Move warning after the intro
This was previously revered due to unintended change in meaning, so I propose it here:
- Warning: AUR helpers are not supported by Arch Linux developers and not present in the official repositories.
- In order to be prepared to troubleshoot problems you should become familiar with the manual build process.
- First you introduce what is AUR helpers, then provide a warning. This is consistent with AUR, Wine articles.
- Merge warning with last intro sentence.
- Move troubleshooting out of the warning as separate and final point in the intro.
Hopefully these make sense, wording is not changed much, except word "developer" after "Arch Linux".
- I question changing the text of the warning. The article contains two "helpers" which are in the repos - devtools and aurpublish - a similar mention is already in AUR_Trusted_User_Guidelines#Rules_for_Packages_Entering_the_.5Bcommunity.5D_Repo, and adding "not in the repos" is more redundant than something that adds strength to the existing warning.
- As to the location of the warning, I would argue the reverse: move the warnings in articles like AUR up, rather than the warning here down. People acknowledging the warning may decide to not more spend any time on the topic at hand. -- Alad (talk) 18:55, 18 May 2019 (UTC)
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.
packer should still be mentioned in the wiki even if it's discontinued
I had no idea where the packer aur package went because **apparently** someone decided to completely remove it from every single mention on the wiki. How was I supposed to know it was discontinued? Do I have to check the edit history just to know? What about all the other people who might still use packer, as there was a fork that has also disappeared in the AUR? Am I supposed to move to a different helper or fork it myself? Absolutely no consideration.