暂无描述

transifex-integration[bot] 3da808847f Updates for file po/en.po in ru_RU (#2574) 2 月之前
.github 3a118b7690 chore: fix failing build actions (#2503) 7 月之前
completions fb168fb176 fix swapped fish completion descriptions for --repo and --aur (#2523) 6 月之前
doc 13df7e79eb Document -Ycc in manpage (#2482) 7 月之前
pkg 3f2f6eae31 socks5 support (#2543) 4 月之前
po 3da808847f Updates for file po/en.po in ru_RU (#2574) 2 月之前
testdata e60ccdf8b7 Fix image recursive build (#2280) 1 年之前
.dockerignore a8ba2a808b fix(docker): fix dockerignore 4 年之前
.gitignore 89b32ee9ce fix(parser): allow disable-sandbox option. fixes #2509 (#2511) 7 月之前
.golangci.yml 3a118b7690 chore: fix failing build actions (#2503) 7 月之前
.pre-commit-config.yaml 26aa171b2b fix(query): remove -debug packages from missing list if base package is installed (#2372) 1 年之前
CONTRIBUTING.md 22c165a11f feat(search): add optional setting that formats each search result on a single line, Part II 3 年之前
Dockerfile fdcf6ef664 ci(yay): add integration test framework (#2178) 1 年之前
LICENSE 59daf46714 Create LICENSE 8 年之前
Makefile 2ff794da32 chore: update go-alpm (#2409) 1 年之前
README.md 69685d0fb5 docs: update README.md (#2564) 3 月之前
ci.Dockerfile 3a118b7690 chore: fix failing build actions (#2503) 7 月之前
clean.go 8916cd174b refactor(yay): move cfg inside of runtime (#2259) 1 年之前
clean_test.go 8916cd174b refactor(yay): move cfg inside of runtime (#2259) 1 年之前
cmd.go 13df7e79eb Document -Ycc in manpage (#2482) 7 月之前
cmd_test.go 8916cd174b refactor(yay): move cfg inside of runtime (#2259) 1 年之前
errors.go 8916cd174b refactor(yay): move cfg inside of runtime (#2259) 1 年之前
get.go a1121556be refactor: remove redundant `len` check (#2291) 1 年之前
go.mod 3f2f6eae31 socks5 support (#2543) 4 月之前
go.sum 3f2f6eae31 socks5 support (#2543) 4 月之前
local_install.go 5d887cbd41 Replace github.com/pkg/errors with stdlib errors/fmt (#2400) 1 年之前
local_install_test.go ec837c831d fix(installer): Fixes the same pkgbase being built multiple times (#2534) 5 月之前
main.go d02c45e5b6 Remove deprecated flags in favor of boolean flags (#2350) 1 年之前
print.go 8916cd174b refactor(yay): move cfg inside of runtime (#2259) 1 年之前
print_test.go 8916cd174b refactor(yay): move cfg inside of runtime (#2259) 1 年之前
query.go 0165486bf4 Respect provided targets when using -Si flag (#2460) 10 月之前
query_test.go 8916cd174b refactor(yay): move cfg inside of runtime (#2259) 1 年之前
sync.go 8916cd174b refactor(yay): move cfg inside of runtime (#2259) 1 年之前
sync_test.go ec837c831d fix(installer): Fixes the same pkgbase being built multiple times (#2534) 5 月之前
vcs.go 8916cd174b refactor(yay): move cfg inside of runtime (#2259) 1 年之前
vote.go 8916cd174b refactor(yay): move cfg inside of runtime (#2259) 1 年之前

README.md

yay yay-bin yay-git AUR votes GitHub license

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 search linux and then narrow on header)
  • 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

asciicast

asciicast

Installation

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

[!WARNING]
We are using sudo 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 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 --gendb to generate a development package database for *-git packages that were installed without yay. This command should only be run once.

  • yay -Syu --devel will then check for development package updates

  • Use yay -Y --devel --save to make development package updates permanently enabled (yay and yay -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 the Color 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 uses git diff to 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 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} --aur yay -{OPERATION} --repo

  • A Flagged 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 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 -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 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 --gendb will 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.

Images

Other AUR helpers/tools