Folders and files

Name		Name	Last commit message	Last commit date
Latest commit History 2,267 Commits
.github		.github
completions		completions
doc		doc
pkg		pkg
po		po
testdata		testdata
.dockerignore		.dockerignore
.gitignore		.gitignore
.golangci.yml		.golangci.yml
.pre-commit-config.yaml		.pre-commit-config.yaml
CONTRIBUTING.md		CONTRIBUTING.md
Dockerfile		Dockerfile
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
ci.Dockerfile		ci.Dockerfile
clean.go		clean.go
clean_test.go		clean_test.go
cmd.go		cmd.go
cmd_test.go		cmd_test.go
errors.go		errors.go
get.go		get.go
go.mod		go.mod
go.sum		go.sum
local_install.go		local_install.go
local_install_test.go		local_install_test.go
main.go		main.go
print.go		print.go
print_test.go		print_test.go
query.go		query.go
query_test.go		query_test.go
sync.go		sync.go
sync_test.go		sync_test.go
vcs.go		vcs.go
vote.go		vote.go

Repository files navigation

Yay

Yet Another Yogurt - An AUR Helper Written in Go

Help translate yay:Transifex

Features

Advanced dependency solving
PKGBUILD downloading from ABS or AUR
Completions for AUR packages
Query user up-front for all input (prior to starting builds)
Narrow search (yay linux header will first searchlinux and then narrow onheader)
Find matching package providers during search and allow selection
Remove make dependencies at the end of the build process
Build local PKGBUILDs with AUR dependencies
Un/Vote for packages

Installation

If you are migrating from another AUR helper, you can simply install Yay with that helper.

Warning

We are usingsudo in these examples, you can switch that out for a different privilege escalation tool.

Source

The initial installation of Yay can be done by cloning the PKGBUILD andbuilding with makepkg:

We make sure we have thebase-devel package group installed.

sudo pacman -S --needed git base-develgit clone https://aur.archlinux.org/yay.gitcd yaymakepkg -si

If you want to do all of this at once, we can chain the commands like so:

sudo pacman -S --needed git base-devel&& git clone https://aur.archlinux.org/yay.git&&cd yay&& makepkg -si

Binary

If you do not want to compile yay yourself you can use the builds generated byGitHub Actions.

sudo pacman -S --needed git base-develgit clone https://aur.archlinux.org/yay-bin.gitcd yay-binmakepkg -si

If you want to do all of this at once, we can chain the commands like so:

sudo pacman -S --needed git base-devel&& git clone https://aur.archlinux.org/yay-bin.git&&cd yay-bin&& makepkg -si

Other distributions

If you're using Manjaro oranother distribution that packagesyayyou can simply install yay using pacman (as root):

pacman -S --needed git base-devel yay

Warning

distributions sometimes lag updating yay on their repositories.

First Use

Development packages upgrade

Useyay -Y --gendb to generate a development package database for*-gitpackages that were installed without yay.This command should only be run once.
yay -Syu --devel will then check for development package updates
Useyay -Y --devel --save to make development package updates permanentlyenabled (yay andyay -Syu will then always check dev packages)

Examples of Custom Operations

Command	Description
`yay`	Alias to`yay -Syu`.
`yay <Search Term>`	Present package-installation selection menu.
`yay -Bi <dir>`	Install dependencies and build a local PKGBUILD.
`yay -G <AUR Package>`	Download PKGBUILD from ABS or AUR. (yay v12.0+)
`yay -Gp <AUR Package>`	Print to stdout PKGBUILD from ABS or AUR.
`yay -Ps`	Print system statistics.
`yay -Syu --devel`	Perform system upgrade, but also check for development package updates.
`yay -Syu --timeupdate`	Perform system upgrade and use PKGBUILD modification time (not version number) to determine update.
`yay -Wu <AUR Package>`	Unvote for package (Requires setting`AUR_USERNAME` and`AUR_PASSWORD` environment variables) (yay v11.3+)
`yay -Wv <AUR Package>`	Vote for package (Requires setting`AUR_USERNAME` and`AUR_PASSWORD` environment variables). (yay v11.3+)
`yay -Y --combinedupgrade --save`	Make combined upgrade the default mode.
`yay -Y --gendb`	Generate development package database used for devel update.
`yay -Yc`	Clean unneeded dependencies.

Frequently Asked Questions

Yay does not display colored output. How do I fix it?
Make sure you have theColor option in your/etc/pacman.conf(see issue#123).
Sometimes diffs are printed to the terminal, and other times they are paged via less. How do I fix this?
Yay usesgit diff to display diffs, which by default tells less not topage if the output can fit into one terminal length. This behavior can beoverridden by exporting your own flags (export LESS=SRX).
Yay is not asking me to edit PKGBUILDS, and I don't like the diff menu! What can I do?
yay --editmenu --diffmenu=false --save
How can I tell Yay to act only on AUR packages, or only on repo packages?
yay -{OPERATION} --auryay -{OPERATION} --repo
AFlagged Out Of Date AUR Packages message is displayed. Why doesn't Yay update them?
This message does not mean that updated AUR packages are available. It meansthe packages have been flagged out of date on the AUR, buttheir maintainers have not yet updated thePKGBUILDs(seeoutdated AUR packages).
Yay doesn't install dependencies added to a PKGBUILD during installation.
Yay resolves all dependencies ahead of time. You are free to edit thePKGBUILD in any way, but any problems you cause are your own and should not bereported unless they can be reproduced with the original PKGBUILD.
I know my-git package has updates but yay doesn't offer to update it
Yay uses a hash cache for development packages. Normally it is updated at the end of the package install with the messageFound 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 --gendb will fix the current version of every devel package and start checking from there.
I want to help out!
CheckCONTRIBUTING.md for more information.

Support

All support related to Yay should be requested via GitHub issues. Since Yay is notofficially supported by Arch Linux, support should not be sought out on theforums, 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 anyother relevant information. Never make reports using Yay or any other externaltools.