Yet another Yogurt - An AUR Helper written in Go
Yet Another Yogurt - An AUR Helper Written in Go
There's a point in everyone's life when you feel the need to write an AUR helper because there are only about 20 of them. So say hi to 20+1.
Yay is based on the design of yaourt, apacman and pacaur. It is developed with these objectives in mind:
yay linux headerwill first search
linuxand then narrow on
header)
If you are migrating from another AUR helper, you can simply install Yay with that helper.
Alternatively, the initial installation of Yay can be done by cloning the PKGBUILD and building with makepkg:
Before you begin, make sure you have the
base-develpackage group installed.
pacman -S --needed git base-devel git clone https://aur.archlinux.org/yay.git cd yay makepkg -si
All support related to Yay should be requested via GitHub issues. Since Yay is not officially supported by Arch Linux, support should not be sought out on the forums, AUR comments or other official channels.
A broken AUR package should be reported as a comment on the package's AUR page. A package may only be considered broken if it fails to build with makepkg. Reports should be made using makepkg and include the full output as well as any other relevant information. Never make reports using Yay or any other external tools.
Make sure you have the
Coloroption in your
/etc/pacman.conf(see issue #123).
The default behavior was changed after v8.918 (see 3bdb534 and issue #554). To restore the package-skip behavior use
--combinedupgrade(make it permanent by appending
--save). Note: skipping packages will leave your system in a partially-upgraded state.
Yay uses
git diffto display diffs, which by default tells less not to page if the output can fit into one terminal length. This behavior can be overridden by exporting your own flags (
export LESS=SRX).
yay --editmenu --nodiffmenu --save
yay -{OPERATION} --aur
yay -{OPERATION} --repo
Out Of Date AUR Packagesmessage is displayed. Why doesn't Yay update them?
This message does not mean that updated AUR packages are available. It means the packages have been flagged out of date on the AUR, but their maintainers have not yet updated the
PKGBUILDs (see outdated AUR packages).
Yay resolves all dependencies ahead of time. You are free to edit the PKGBUILD in any way, but any problems you cause are your own and should not be reported unless they can be reproduced with the original PKGBUILD.
-gitpackage has updates but yay doesn't offer to update it
Yay uses an hash cache for development packages. Normally it is updated at the end of the package install with the message
Found git repo. If you transition between aur helpers and did not install the devel package using yay at some point, it is possible it never got added to the cache.
yay -Y --gendbwill fix the current version of every devel package and start checking from there.
Check CONTRIBUTING.md for more information.
| Command | Description | | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | |
yay| Present package-installation selection menu. | |
yay -Ps| Print system statistics. | |
yay -Yc| Clean unneeded dependencies. | |
yay -G| Download PKGBUILD from ABS or AUR. | |
yay -Y --gendb| Generate development package database used for devel update. | |
yay -Syu --devel --timeupdate| Perform system upgrade, but also check for development package updates and use PKGBUILD modification time (not version number) to determine update. |