Motivation With separatesources enabled (the default), a package with the exact searched name that exists in several sync repos can be listed in the wrong order. For example, if [cachyos-extra-v3] comes before [extra] in pacman.conf, extra/chromium can still show up as the top pick instead of cachyos-extra-v3/chromium. pacman prefers the repo listed first. separateSourceScore returned a flat 50 for every exact match, whatever its source. As a result, all exact matches got the same metric (50 + 1.0). The unstable slices.SortFunc then left their relative order unspecified, so the ordering added for non-exact results did not apply to exact ones. Approach Move the repo-order scoring into a repoOrderScore helper (same logic and cache as before). For exact matches, add repoOrderScore/separateSourceMax to the 50: a bonus between 0 and 1. Exact matches still outrank every non-exact result (which scores at most 45 + a metric below 1). Among exact matches, repos earlier in pacman.conf now come first. Exact AUR matches keep 50, so an exact sync-repo match now ranks strictly above an exact AUR match instead of tying with it. Scoring for non-exact results is unchanged, and nothing changes when separatesources is disabled. Validation - go test -race ./pkg/query/... -count=1: passes. - New tests TestSourceQueryBuilderExactMatchSortsByRepoOrder (top-down and bottom-up) and TestSeparateSourceScore_ExactMatchKeepsRepoOrder fail with the previous metric.go and pass with this change. - golangci-lint run ./pkg/query/...: 0 issues; gofmt clean. - go test ./... on macOS has failures that also occur on the unchanged base: Linux-only syscall fields in pkg/settings/exe, and a timezone-dependent test in pkg/text. Not tested against a real pacman setup with custom repos. Report: https://github.com/Jguer/yay/issues/2986 Assisted-by: claude-opus-5-5 (via Claude Code) Signed-off-by: Pujitha Paladugu <10557236+pujitha24@users.noreply.github.com> Co-authored-by: Pujitha Paladugu <10557236+pujitha24@users.noreply.github.com>
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 headerwill first searchlinuxand 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 using
sudoin 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 and building with makepkg:
We make sure we have the base-devel package group installed.
sudo pacman -S --needed git base-devel
git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -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 by GitHub Actions.
sudo pacman -S --needed git base-devel
git clone https://aur.archlinux.org/yay-bin.git
cd yay-bin
makepkg -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 or another distribution that packages yay
you 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
-
Use
yay -Y --gendbto generate a development package database for*-gitpackages that were installed without yay. This command should only be run once. -
yay -Syu --develwill then check for development package updates -
Use
yay -Y --devel --saveto make development package updates permanently enabled (yayandyay -Syuwill 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 -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 the
Coloroption in your/etc/pacman.conf(see issue #123). -
How do I change the pager used for PKGBUILD diffs?
Diffs for all selected packages are collected and shown in a single pager session. Set
pagerinconfig.jsonoryay.opt.pagerininit.lua, or setPAGERto override the default (less, orcatif less is unavailable). Example:yay.opt.pager = "delta"orexport PAGER=less. -
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 -
A
Flagged 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 doesn't install dependencies added to a PKGBUILD during installation.
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.
-
I know my
-gitpackage has updates but yay doesn't offer to update ityay uses a 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. -
I want to help out!
Check CONTRIBUTING.md for more information.
Support
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.



