YAY(8)

πŸ“¦
version 13.0.1 Β· 2 versions
, in nixpkgs unstable

πŸ¦‹ YAY(8) β€” Yay Manual πŸ¦‹

okay bestie, welcome to the yay(8) manpage, the ✨glow-up✨ edition. yay is an AUR Helper written in go, and this is its manual. let's get into it πŸ’…


✨ NAME ✨

yay β€” AUR Helper written in go. that's the whole vibe. she's an AUR helper, she's written in go, she's iconic. 🫢


✨ SYNOPSIS ✨

yay <operation> [options] [targets]

yay <search terms>

yay

✨ DESCRIPTION ✨

so basically πŸ’β€β™€οΈ Yay is a Pacman wrapper with AUR support. what that means is she passes options to Makepkg and Pacman after resolving packages to install/upgrade. no cap, she does the middle-woman thing and she does it flawlessly.

⚠️ heads up bestie: this manpage only covers options unique to Yay. for the other options (the pacman ones, yk), go check pacman(8). ✨

πŸŽ€ YAY OPERATIONS πŸŽ€

  • -Y, --yay β€” Perform yay specific operations. This one is the default if no other operation is selected and targets are defined. she's the main character 😌
  • -B, --build β€” Build a PKGBUILD in a given directory. πŸ”¨
  • -P, --show β€” Perform yay specific print operations. πŸ–¨οΈ
  • -G, --getpkgbuild β€” Downloads PKGBUILD from ABS or AUR. The ABS can only be used for Arch Linux repositories. iykyk 🧚
  • -W, --web β€” Web related operations such as voting for AUR packages. 🌐

also, super important:

  • If no operation is specified yay -Syu will be performed
  • If no operation is specified and targets are provided -Y will be assumed

πŸ”₯ EXTENDED PACMAN OPERATIONS πŸ”₯

  • -S, -Si, -Sl, -Ss, -Su, -Sc, -Qu β€” These operations are extended to support both AUR and repo packages. both! at once! she's versatile πŸ’…
  • -Sc β€” Yay will also clean cached AUR package and any untracked Files in the cache. ngl, cleaning untracked files will wipe any downloaded sources or built packages but will keep already downloaded vcs sources. so like, don't panic about your vcs sources, but DO be aware 😭
  • -R β€” Yay will also remove cached data about devel packages. πŸ—‘οΈ

🌸 NEW OPTIONS 🌸

  • -N, --repo β€” Assume all targets are from the repositories. Additionally Actions such as sysupgrade will only act on repository packages. strictly repos, no AUR drama πŸ’β€β™€οΈ
  • -a, --aur β€” Assume all targets are from the AUR. Additionally Actions such as sysupgrade will only act on AUR packages.
πŸ“Œ plot twist: note that dependency resolving will still act normally and include repository packages. so she's AUR-only for the vibes, but deps still get their repo moment fr fr.

πŸ“ YAY OPTIONS (APPLY TO -Y AND --YAY) πŸ“

  • <NO OPTION> β€” Displays a list of packages matching the search terms and prompts the user on which packages to install (yogurt mode πŸ₯£). The first search term is used to query the different sources and the following search terms are used to narrow the search results through exact matching. so like, first term = the search, the rest = the filter πŸ’–
  • --gendb β€” Generate development package database. Tracks the latest commit for each development package, when there is a new commit Yay will know to update. This is done per package whenever a package is synced. This option should only be used when migrating to Yay from another AUR helper. πŸ‘‘
  • -c, --clean β€” Remove unneeded dependencies. bye girlie ✌️
  • -cc β€” Remove unneeded dependencies, including packages optionally required by any other package. she's thorough. she's not leaving anything behind πŸ’€

🧚 SHOW OPTIONS (APPLY TO -P AND --show) 🧚

  • -c, --complete β€” Print a list of all AUR and repo packages. This allows shell completion and is not intended to be used directly by the user. it's for the shell, bestie, not for you πŸ™ˆ
  • -d, --defaultconfig β€” Print default yay configuration. ✨
  • -g, --currentconfig β€” Print current yay configuration. ✨
  • -s, --stats β€” Displays information about installed packages and system health. If there are orphaned, or out-of-date packages, or packages that no longer exist on the AUR; warnings will be displayed. she's giving doctor energy 🩺
  • -w, --news β€” Print new news from the Archlinux homepage. News is considered new if it is newer than the build date of all native packages. Pass this twice to show all available news. πŸ“°
  • -q, --quiet β€” Only show titles when printing news. minimal queen πŸŽ€

⭐ BUILD OPTIONS (APPLY TO -B AND --build) ⭐

  • -i, --install β€” Build and install a PKGBUILD in a given directory. build AND install, she does both 🫢

🌈 GETPKGBUILD OPTIONS (APPLY TO -G AND --getpkgbuild) 🌈

  • -f, --force β€” Force download for ABS packages that already exist in the current directory. This ensures directories are not accidentally overwritten. bold of it to force, but protective of your files, we love a careful icon πŸ’…
  • -p, --print β€” Prints the PKGBUILD of the given packages to stdout. πŸ’»

πŸ‘‘ WEB OPTIONS (APPLY TO -W AND --web) πŸ‘‘

Web related operations such as voting for AUR packages. Requires setting AUR_USERNAME and AUR_PASSWORD environment variables. set 'em or she can't log in, periodt πŸ”‘

  • -u, --unvote β€” Remove vote from AUR package(s). takebacks are valid πŸ’”
  • -v, --vote β€” Vote for AUR package(s). show some love πŸ—³οΈπŸ’–

πŸ’œ PERMANENT CONFIGURATION SETTINGS πŸ’œ

  • --save β€” Causes the following options to be saved back to the config file. This provides an easy way to change config options without directly editing the file. the lazy girlie's dream, and honestly? valid πŸ’…
  • --aururl β€” Set an alternative AUR URL.
  • --aurrpcurl β€” Set an alternative URL for the AUR /rpc endpoint.
  • --builddir <dir> β€” Directory to use for Building AUR Packages. This directory is also used as the AUR cache when deciding if Yay should skip builds.
  • --editor <command> β€” Editor to use when editing PKGBUILDs. If this is not set the VISUAL environment variable will be checked, followed by EDITOR. If none of these are set Yay will prompt the user for an editor.
  • --editorflags <flags> β€” Passes arguments to the editor. These flags get passed to every instance where the editor is called by Yay. Arguments are split on whitespace before being passed to the editor. Multiple arguments may be passed by supplying a space separated list that is quoted by the shell.
  • --makepkg <command> β€” The command to use for makepkg calls. This can be a command in PATH or an absolute path to the file.
  • --pacman <command> β€” The command to use for pacman calls. This can be a command in PATH or an absolute path to the file.
  • --git <command> β€” The command to use for git calls. This can be a command in PATH or an absolute path to the file.
  • --gitflags <flags> β€” Passes arguments to git. These flags get passed to every instance where git is called by yay. Arguments are split on whitespace before being passed to git. Multiple arguments may be passed by supplying a space separated list that is quoted by the shell.
  • --gpg <command> β€” The command to use for gpg calls. This can be a command in PATH or an absolute path to the file.
  • --config <file> β€” The pacman config file to use.
  • --makepkgconf <file> β€” The config file for makepkg to use. If this is not set then the default config file will be used.
  • --nomakepkgconf β€” Reset the makepkg config file back to its default. πŸŽ€
  • --requestsplitn <number> β€” The maximum amount of packages to request per AUR query. The higher the number the faster AUR requests will be. Requesting too many packages in one AUR query will cause an error. This should only make a noticeable difference with very large requests (>500) packages.
  • --completioninterval <days> β€” Time in days to refresh the completion cache. Setting this to 0 will cause the cache to be refreshed every time, while setting this to -1 will cause the cache to never be refreshed. extremes only, love that for her πŸ¦‹
  • --sortby <votes|popularity|name|base|submitted|modified> β€” Sort AUR results by a specific field during search.
  • --searchby <name|name-desc|maintainer|depends|checkdepends|makedepends|optdepends|provides|conflicts|replaces|groups|keywords|comaintainers> β€” Search for AUR packages by querying the specified field.
  • --answerclean <All|None|Installed|NotInstalled|...> β€” Set a predetermined answer for the clean build menu question. This answer will be used instead of reading from standard input but will be parsed exactly the same.
  • --answerdiff <All|None|Installed|NotInstalled|...> β€” Set a predetermined answer for the edit diff menu question. This answer will be used instead of reading from standard input but will be parsed exactly the same.
  • --answeredit <All|None|Installed|NotInstalled|...> β€” Set a predetermined answer for the edit pkgbuild menu question. This answer will be used instead of reading from standard input but will be parsed exactly the same.
  • --answerupgrade <Repo|^Repo|None|...> β€” Set a predetermined answer for the upgrade menu question. Selects which package ranges or repos to omit for updates. This answer will be used instead of reading from standard input but will be treated exactly the same.
  • --noanswerclean β€” Unset the answer for the clean build menu.
  • --noanswerdiff β€” Unset the answer for the diff menu.
  • --noansweredit β€” Unset the answer for the edit pkgbuild menu.
  • --noanswerupgrade β€” Unset the answer for the upgrade menu.
  • --cleanmenu β€” Show the clean menu. This menu gives you the chance to fully delete the downloaded build files from Yay's cache before redownloading a fresh copy.
πŸ’‘ if cleanmenu is enabled in the configuration file, you can temporarily disable it by using --cleanmenu=false on the command line. sneaky sneaky, love that πŸ™ˆ
  • --diffmenu β€” Show the diff menu. This menu gives you the option to view diffs from build files before building.

Diffs are shown via git diff which uses less by default. This behaviour can be changed via git's config, the $GIT_PAGER or $PAGER environment variables. πŸŽ€

  • --editmenu β€” Show the edit menu. This menu gives you the option to edit or view PKGBUILDs before building.
⚠️ Warning: Yay resolves dependencies ahead of time via the RPC. It is not recommended to edit pkgbuild variables unless you know what you are doing. fr fr, don't touch what you don't understand bestie 😭
  • --askremovemake β€” Ask to remove makedepends after installing packages.
  • --askyesremovemake β€” Ask to remove makedepends after installing packages(with "Y" as default). 🫢
  • --removemake β€” Remove makedepends after installing packages.
  • --noremovemake β€” Do not remove makedepends after installing packages.
  • --topdown β€” Display repository packages first and then AUR packages. ⬇️
  • --bottomup β€” Show AUR packages first and then repository packages. ⬆️
  • --singlelineresults β€” Override pacman's usual double-line search result format and list each result on its own line.
  • --doublelineresults β€” Follow pacman's double-line search result format and list each result using two lines.
  • --devel β€” During sysupgrade also check AUR development packages for updates. Currently only Git packages are supported.

Devel checking is done using git ls-remote. The newest commit hash is compared against the hash at install time. This allows devel updates to be checked almost instantly and not require the original pkgbuild to be downloaded. literally so fast, she ate πŸ”₯

okay so bestie, picking up right where we left off on the devel tea β˜• β€” the slower pacaur-like devel checks can be done manually by piping a list of packages into yay (peep the examples below, they're giving ✨). And if 'devel' is enabled in the config file, you can temporarily turn it off with --devel=false right on the command line. Slay.

and now the rest of the option menu, no skips, no cap:

  • --cleanafter β€” removes untracked files after installation. untracked files get yeeted except directories. why? so VCS packages can easily pull an update instead of having to reclone the entire repo. iconic behavior πŸ’…
  • --keepsrc β€” keeps pkg/ and src/ after building packages. simple as that.
  • --separatesources β€” separates query results by source: AUR and sync. two piles, no mixing.
  • --redownload β€” always downloads pkgbuilds of targets even when a copy is already chilling in cache.
  • --redownloadall β€” always downloads pkgbuilds of all AUR packages even when a copy is available in cache.
  • --noredownload β€” when downloading pkgbuilds, if the pkgbuild is found in cache and is equal or newer than the AUR's version, use that instead of downloading a new one. lowkey efficient.
  • --provides β€” looks for matching providers when searching for AUR packages. when multiple providers are found, a menu pops up prompting you to pick one. this increases dependency resolve time although this should not be noticeable.
  • --pgpfetch β€” prompts to import unknown PGP keys from the validpgpkeys field of each PKGBUILD. trust issues? handled.
  • --useask β€” uses pacman's --ask flag to automatically confirm package conflicts. Yay lists conflicts ahead of time. it is possible that Yay does not detect a conflict, causing a package to be removed without the user's confirmation. however, this is very unlikely. so like, don't stress? but also know the risk.
  • --combinedupgrade β€” during sysupgrade, Yay will first perform a refresh, then show its combined menu of repo and AUR packages that will be upgraded. then after reviewing the pkgbuilds, the repo and AUR upgrade will start with no need for manual intervention. BUT if Yay exits for any reason after the refresh without upgrading, it is then the user's responsibility to either resolve the reason Yay exited or run a sysupgrade through pacman directly. so don't just walk away mid-upgrade, bestie 😭
  • --batchinstall β€” when building and installing AUR packages, instead of installing each package after building, queue each package for install. then once either all packages are built or a package in the build queue is needed as a dependency to build another package, install all the packages in the install queue. it's giving assembly line realness 🏭
  • --rebuild β€” always builds target packages even when a copy is available in cache.
  • --rebuildall β€” always builds all AUR packages even when a copy is available in cache.
  • --rebuildtree β€” when installing an AUR package, rebuild and reinstall all of its AUR dependencies recursively, even the ones already installed. this flag allows you to easily rebuild packages against your current system's libraries if they have become incompatible. so if your libs are acting brand new, this is the move.
  • --norebuild β€” when building packages, if the package is found in cache and is an equal version to the one wanted, skip the package build and use the existing package.
  • --mflags <flags> β€” passes arguments to makepkg. these flags get passed to every instance where makepkg is called by Yay. arguments are split on whitespace before being passed to makepkg. multiple arguments may be passed by supplying a space separated list that is quoted by the shell.
  • --gpgflags <flags> β€” passes arguments to gpg. these flags get passed to every instance where gpg is called by Yay. arguments are split on whitespace before being passed to gpg. multiple arguments may be passed by supplying a space separated list that is quoted by the shell.
  • --sudo <command> β€” the command to use for sudo calls. this can be a command in PATH or an absolute path to the file. the sudoloop is not guaranteed to work with a custom sudo command.
  • --sudoflags <flags> β€” passes arguments to sudo. these flags get passed to every instance where sudo is called by Yay. arguments are split on whitespace before being passed to sudo. multiple arguments may be passed by supplying a space separated list that is quoted by the shell.
  • --sudoloop β€” loops sudo calls in the background to prevent sudo from timing out during long builds. no more coming back to a dead sudo prompt πŸ’€

πŸ’– EXAMPLES πŸ’–

  • yay foo β€” search and install from the repos and the AUR using yogurt mode. yes, yogurt mode. it's a vibe.
  • yay -Syu β€” update package list and upgrade all currently installed repo and AUR packages.
  • yay -Sua β€” update all currently installed AUR packages.
  • yay -S foo β€” installs package foo from the repos or the AUR.
  • yay -Ss foo β€” searches for package foo on the repos or the AUR.
  • yay -Si foo β€” gets information about package foo from the repos or the AUR.
  • yay -S foo --mflags "--skipchecksums --skippgpcheck" β€” installs foo while skipping checksums and pgp checks. risky? maybe. iconic? absolutely.
  • yay --devel --save β€” sets devel to true in the config.
  • yay -P --stats β€” shows statistics for installed packages and system health. know your numbers, bestie πŸ“Š
  • pacman -Qmq | grep -Ee '-(cvs|svn|git|hg|bzr|darcs)$' | yay -S --needed - β€” pacaur-like devel check. pipe it, don't fight it.

🌈 ENVIRONMENT VARIABLES 🌈

  • AURDEST β€” can be set to configure the build directory. overridden by --builddir.
  • VISUAL, EDITOR β€” when editor is not configured, use these variables to pick what editor to use when editing PKGBUILDS. so like, tell Yay who your fave editor is πŸ’…

πŸ—‚οΈ FILES πŸ—‚οΈ

πŸ“ CONFIG DIRECTORY πŸ“

the config directory is $XDG_CONFIG_HOME/yay/. if $XDG_CONFIG_HOME is unset, the config directory will fall back to $HOME/.config/yay.

config.json is used to store all of Yay's config options. editing this file should be done through Yay, using the options mentioned in PERMANENT CONFIGURATION SETTINGS. don't raw-dog the JSON unless you know what you're doing, bestie.

init.lua can set Lua configuration options and define Lua hooks, such as pre-install hooks for AUR PKGBUILDs. see doc/lua.md for the Lua API. yes, Lua. we're fancy now 🧚

πŸ“ CACHE DIRECTORY πŸ“

the cache directory is $XDG_CACHE_HOME/yay/. if $XDG_CACHE_HOME is unset, the cache directory will fall back to $HOME/.cache/yay.

completion.cache holds a list of of all packages, including the AUR, for shell completion. by default the completion files are refreshed every 7 days. (yes, double "of" β€” it's a whole thing, we move.)

vcs.json tracks VCS packages and the latest commit of each source. if any of these commits change, the package will be upgraded during a devel update. so that's how the devel magic knows πŸ‘€

πŸ“ BUILD DIRECTORY πŸ“

unless otherwise set, this should be the same as CACHE DIRECTORY. this directory is used to store downloaded AUR Packages as well as any source files and built packages from those packages.

πŸ“ PACMAN.CONF πŸ“

Yay uses Pacman's config file to set certain pacman options either through go-alpm or Yay itself. options inherited include most libalpm options and pacman options.

notably: Databases, Color and *Path/*Dir options are used.


πŸ”— SEE ALSO πŸ”—

makepkg(8), makepkg.conf(5), PKGBUILD(5), pacman(8), pacman.conf(5)

see the arch wiki at https://wiki.archlinux.org/index.php/Arch_User_Repository for more info on the AUR. wiki bestie, we love you 🌸


🐞 BUGS 🐞

please report bugs to our GitHub page https://github.com/Jguer/yay β€” they're not scary, they're just misunderstood 🫢


πŸ‘‘ AUTHORS πŸ‘‘

  • Jguer <joguer@proton.me>
  • Morgan <morganamilo@archlinux.org>

and that's the whole manual, bestie! this masterpiece is Yay v13.0+, dated 2026-06-17, and it lives in section YAY(8) of the manual. go forth and slay your packages πŸ’…βœ¨πŸ’–

πŸ“¦ where this page comes from