Guest User

Untitled

a guest
Oct 15th, 2019
383
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 19.22 KB | None | 0 0
  1. YAY(8) Yay Manual YAY(8)
  2.  
  3. NAME
  4. yay - AUR Helper written in go
  5.  
  6. SYNOPSIS
  7. yay <operation> [options] [targets]
  8.  
  9. yay <search terms>
  10.  
  11. yay
  12.  
  13. DESCRIPTION
  14. Yay is a Pacman wrapper with AUR support. It passes options to Makepkg and Pacman after resolving packages to
  15. install/upgrade.
  16.  
  17. This manpage only covers options unique to Yay. For other options see pacman(8).
  18.  
  19. YAY OPERATIONS
  20. -Y, --yay
  21. Perform yay specific operations. This is the default if no other operation is selected.
  22.  
  23. -P, --show
  24. Perform yay specific print operations.
  25.  
  26. -G, --getpkgbuild
  27. Downloads PKGBUILD from ABS or AUR. ABS pkgbuilds are always downloaded using tarballs and taken from trunk.
  28. The ABS can only be used for Arch Linux repositories
  29.  
  30. If no arguments are provided 'yay -Syu' will be performed.
  31.  
  32. If no operation is selected -Y will be assumed.
  33.  
  34. EXTENDED PACMAN OPERATIONS
  35. -S, -Si, -Sl, -Ss, -Su, -Sc, -Qu
  36. These operations are extended to support both AUR and repo packages.
  37.  
  38. -Sc Yay will also clean cached AUR package and any untracked Files in the cache. Untracked files cleaning only
  39. works for packages downloaded using gitclone. Cleaning untracked files will wipe any downloaded sources or
  40. built packages but will keep already downloaded vcs sources.
  41.  
  42. -R Yay will also remove cached data about devel packages.
  43.  
  44. NEW OPTIONS
  45. --repo Assume all targets are from the repositories. Additionally Actions such as sysupgrade will only act on
  46. repository packages.
  47.  
  48. -a, --aur
  49. Assume all targets are from the AUR. Additionally Actions such as sysupgrade will only act on AUR packages.
  50.  
  51. Note that dependency resolving will still act normally and include repository packages.
  52.  
  53. YAY OPTIONS (APPLY TO -Y AND --YAY)
  54. <NO OPTION>
  55. Displays a list of packages matching the search terms and prompts the user on which packages to install
  56. (yogurt mode).
  57.  
  58. --gendb
  59. Generate development package database. Tracks the latest commit for each development package, when there is
  60. a new commit Yay will know to update. This is done per package whenever a package is synced. This option
  61. should only be used when migrating to Yay from another AUR helper.
  62.  
  63. -c, --clean
  64. Remove unneeded dependencies.
  65.  
  66. SHOW OPTIONS (APPLY TO -P AND --SHOW)
  67. -c, --complete
  68. Print a list of all AUR and repo packages. This allows shell completion and is not intended to be used
  69. directly by the user.
  70.  
  71. -f, --fish
  72. During complete adjust the output for the fish shell.
  73.  
  74. -d, --defaultconfig
  75. Print default yay configuration.
  76.  
  77. -g, --currentconfig
  78. Print current yay configuration.
  79.  
  80. -n, --numberupgrades
  81. Deprecated, use yay -Qu and wc -l instead.
  82.  
  83. -s, --stats
  84. Displays information about installed packages and system health. If there are orphaned, or out-of-date
  85. packages, or packages that no longer exist on the AUR; warnings will be displayed.
  86.  
  87. -u, --upgrades
  88. Deprecated, use yay -Qu instead.
  89.  
  90. -w, --news
  91. Print new news from the Archlinux homepage. News is considered new if it is newer than the build date of all
  92. native packages. Pass this twice to show all available news.
  93.  
  94. -q, --quiet
  95. Only show titles when printing news.
  96.  
  97. GETPKGBUILD OPTIONS (APPLY TO -G AND --GETPKGBUILD)
  98. -f, --force
  99. Force download for packages that already exist in the current directory. This ensures directories are not
  100. accidentally overwritten. This option is not needed for git based downloads as git pull already has safety
  101. mechanisms.
  102.  
  103. PERMANENT CONFIGURATION SETTINGS
  104. --save Causes the following options to be saved back to the config file. This provides an easy way to change config
  105. options without directly editing the file.
  106.  
  107. --aururl
  108. Set an alternative AUR URL. This is mostly useful for users in China who wish to use
  109. https://aur.tuna.tsinghua.edu.cn/.
  110.  
  111. --builddir <dir>
  112. Directory to use for Building AUR Packages. This directory is also used as the AUR cache when deciding if
  113. Yay should skip builds.
  114.  
  115. --editor <command>
  116. Editor to use when editing PKGBUILDs. If this is not set the EDITOR environment variable will be checked,
  117. followed by VISUAL. If none of these are set Yay will prompt the user for an editor.
  118.  
  119. --editorflags <flags>
  120. Passes arguments to the editor. These flags get passed to every instance where the editor is called by Yay.
  121. Arguments are split on whitespace before being passed to the editor. Multiple arguments may be passed by
  122. supplying a space separated list that is quoted by the shell.
  123.  
  124. --makepkg <command>
  125. The command to use for makepkg calls. This can be a command in PATH or an absolute path to the file.
  126.  
  127. --pacman <command>
  128. The command to use for pacman calls. This can be a command in PATH or an absolute path to the file.
  129.  
  130. --tar <command>
  131. The command to use for bsdtar calls. This can be a command in PATH or an absolute path to the file.
  132.  
  133. --git <command>
  134. The command to use for git calls. This can be a command in PATH or an absolute path to the file.
  135.  
  136. --gpg <command>
  137. The command to use for gpg calls. This can be a command in PATH or an absolute path to the file.
  138.  
  139. --config <file>
  140. The pacman config file to use.
  141.  
  142. --makepkgconf <file>
  143. The config file for makepkg to use. If this is not set then the default config file will be used.
  144.  
  145. --nomakepkgconf
  146. Reset the makepkg config file back to its default.
  147.  
  148. --requestsplitn <number>
  149. The maximum amount of packages to request per AUR query. The higher the number the faster AUR requests will
  150. be. Requesting too many packages in one AUR query will cause an error. This should only make a noticeable
  151. difference with very large requests (>500) packages.
  152.  
  153. --completioninterval <days>
  154. Time in days to refresh the completion cache. Setting this to 0 will cause the cache to be refreshed every
  155. time, while setting this to -1 will cause the cache to never be refreshed.
  156.  
  157. --sortby <votes|popularity|id|baseid|name|base|submitted|modified>
  158. Sort AUR results by a specific field during search.
  159.  
  160. --answerclean <All|None|Installed|NotInstalled|...>
  161. Set a predetermined answer for the clean build menu question. This answer will be used instead of reading
  162. from standard input but will be parsed exactly the same.
  163.  
  164. --answerdiff <All|None|Installed|NotInstalled|...>
  165. Set a predetermined answer for the edit diff menu question. This answer will be used instead of reading from
  166. standard input but will be parsed exactly the same.
  167.  
  168. --answeredit <All|None|Installed|NotInstalled|...>
  169. Set a predetermined answer for the edit pkgbuild menu question. This answer will be used instead of reading
  170. from standard input but will be parsed exactly the same.
  171.  
  172. --answerupgrade <Repo|^Repo|None|...>
  173. Set a predetermined answer for the upgrade menu question. Selects which package ranges or repos to omit for
  174. updates. This answer will be used instead of reading from standard input but will be treated exactly the
  175. same.
  176.  
  177. --noanswerclean
  178. Unset the answer for the clean build menu.
  179.  
  180. --noanswerdiff
  181. Unset the answer for the diff menu.
  182.  
  183. --noansweredit
  184. Unset the answer for the edit pkgbuild menu.
  185.  
  186. --noanswerupgrade
  187. Unset the answer for the upgrade menu.
  188.  
  189. --cleanmenu
  190. Show the clean menu. This menu gives you the chance to fully delete the downloaded build files from Yay's
  191. cache before redownloading a fresh copy.
  192.  
  193. --diffmenu
  194. Show the diff menu. This menu gives you the option to view diffs from build files before building.
  195.  
  196. Diffs are shown via git diff which uses less by default. This behaviour can be changed via git's config, the
  197. $GIT_PAGER or $PAGER environment variables.
  198.  
  199. --editmenu
  200. Show the edit menu. This menu gives you the option to edit or view PKGBUILDs before building.
  201.  
  202. Warning: Yay resolves dependencies ahead of time via the RPC. It is not recommended to edit pkgbuild
  203. variables unless you know what you are doing.
  204.  
  205. --upgrademenu
  206. Show a detailed list of updates in a similar format to VerbosePkgLists. Upgrades can also be skipped using
  207. numbers, number ranges or repo names. Additionally ^ can be used to invert the selection.
  208.  
  209. Warning: It is not recommended to skip updates from the repositories as this can lead to partial upgrades.
  210. This feature is intended to easily skip AUR updates on the fly that may be broken or have a long compile
  211. time. Ultimately it is up to the user what upgrades they skip.
  212.  
  213. --nocleanmenu
  214. Do not show the clean menu.
  215.  
  216. --nodiffmenu
  217. Do not show the diff menu.
  218.  
  219. --noeditmenu
  220. Do not show the edit menu.
  221.  
  222. --noupgrademenu
  223. Do not show the upgrade menu.
  224.  
  225. --askremovemake
  226. Ask to remove makedepends after installing packages.
  227.  
  228. --removemake
  229. Remove makedepends after installing packages.
  230.  
  231. --noremovemake
  232. Do not remove makedepends after installing packages.
  233.  
  234. --topdown
  235. Display repository packages first and then AUR packages.
  236.  
  237. --bottomup
  238. Show AUR packages first and then repository packages.
  239.  
  240. --devel
  241. During sysupgrade also check AUR development packages for updates. Currently only Git packages are
  242. supported.
  243.  
  244. Devel checking is done using git ls-remote. The newest commit hash is compared against the hash at install
  245. time. This allows devel updates to be checked almost instantly and not require the original pkgbuild to be
  246. downloaded.
  247.  
  248. The slower pacaur-like devel checks can be implemented manually by piping a list of packages into yay (see
  249. examples).
  250.  
  251. --nodevel
  252. Do not check for development packages updates during sysupgrade.
  253.  
  254. --gitclone
  255. Use git to download and update PKGBUILDs. PKGBUILDs previously downloaded using tarball will continue to use
  256. tarballs until the package is clean built. Similarly, PKGBUILDs managed with git will continue to use git
  257. until the package is clean built..
  258.  
  259. --nogitclone
  260. Download and update PKGBUILDs using tarballs. The above conditions about previously installed packages still
  261. apply.
  262.  
  263. --cleanafter
  264. Remove package sources after successful Install.
  265.  
  266. For packages downloaded through git, untracked files are removed with the exception of directories. This
  267. allows VCS packages to easily pull an update instead of having to re clone the entire repo.
  268.  
  269. For packages downloaded via tarball, the entire directory is deleted.
  270.  
  271. --nocleanafter
  272. Do not remove package sources after successful Install.
  273.  
  274. --timeupdate
  275. During sysupgrade also compare the build time of installed packages against the last modification time of
  276. each package's AUR page.
  277.  
  278. --notimeupdate
  279. Do not consider build times during sysupgrade.
  280.  
  281. --redownload
  282. Always download pkgbuilds of targets even when a copy is available in cache.
  283.  
  284. --redownloadall
  285. Always download pkgbuilds of all AUR packages even when a copy is available in cache.
  286.  
  287. --noredownload
  288. When downloading pkgbuilds if the pkgbuild is found in cache and is equal or newer than the AUR's version
  289. use that instead of downloading a new one.
  290.  
  291. --provides
  292. Look for matching providers when searching for AUR packages. When multiple providers are found a menu will
  293. appear prompting you to pick one. This increases dependency resolve time although this should not be
  294. noticeable.
  295.  
  296. --noprovides
  297. Do not look for matching providers when searching for AUR packages. Yay will never show its provider menu
  298. but Pacman will still show its provider menu for repo packages.
  299.  
  300. --pgpfetch
  301. Prompt to import unknown PGP keys from the validpgpkeys field of each PKGBUILD.
  302.  
  303. --nopgpfetch
  304. Do not prompt to import unknown PGP keys. This is likely to cause a build failure unless using options such
  305. as --skippgpcheck or a customized gpg config.
  306.  
  307. --useask
  308. Use pacman's --ask flag to automatically confirm package conflicts. Yay lists conflicts ahead of time. It is
  309. possible that Yay does not detect a conflict, causing a package to be removed without the user's
  310. confirmation. However, this is very unlikely.
  311.  
  312. --nouseask
  313. Manually resolve package conflicts during the install. Packages which do not conflict will not need to be
  314. confined manually.
  315.  
  316. --combinedupgrade
  317. During sysupgrade, Yay will first perform a refresh, then show its combined menu of repo and AUR packages
  318. that will be upgraded. Then after reviewing the pkgbuilds, the repo and AUR upgrade will start with no need
  319. for manual intervention.
  320.  
  321. If Yay exits for any reason After the refresh without upgrading. It is then the user's responsibility to
  322. either resolve the reason Yay exited or run a sysupgrade through pacman directly.
  323.  
  324. --nocombinedupgrade
  325. During sysupgrade, Pacman -Syu will be called, then the AUR upgrade will start. This means the upgrade menu
  326. and pkgbuild review will be performed after the sysupgrade has finished.
  327.  
  328. --rebuild
  329. Always build target packages even when a copy is available in cache.
  330.  
  331. --rebuildall
  332. Always build all AUR packages even when a copy is available in cache.
  333.  
  334. --rebuildtree
  335. When installing an AUR package rebuild and reinstall all of its AUR dependencies recursively, even the ones
  336. already installed. This flag allows you to easily rebuild packages against your current system's libraries
  337. if they have become incompatible.
  338.  
  339. --norebuild
  340. When building packages if the package is found in cache and is an equal version to the one wanted skip the
  341. package build and use the existing package.
  342.  
  343. --mflags <flags>
  344. Passes arguments to makepkg. These flags get passed to every instance where makepkg is called by Yay.
  345. Arguments are split on whitespace before being passed to makepkg. Multiple arguments may be passed by
  346. supplying a space separated list that is quoted by the shell.
  347.  
  348. --gpgflags <flags>
  349. Passes arguments to gpg. These flags get passed to every instance where gpg is called by Yay. Arguments are
  350. split on whitespace before being passed to gpg. Multiple arguments may be passed by supplying a space
  351. separated list that is quoted by the shell.
  352.  
  353. --sudoloop
  354. Loop sudo calls in the background to prevent sudo from timing out during long builds.
  355.  
  356. --nosudoloop
  357. Do not loop sudo calls in the background.
  358.  
  359. EXAMPLES
  360. yay foo
  361. Search and install from the repos and the AUR using yogurt mode.
  362.  
  363. yay -Syu
  364. Update package list and upgrade all currently installed repo and AUR.
  365.  
  366. yay -Sua
  367. Update all currently installed AUR packages.
  368.  
  369. yay -S foo
  370. Installs package foo from the repos or the AUR.
  371.  
  372. yay -Ss foo
  373. Searches for package foo on the repos or the AUR.
  374.  
  375. yay -Si foo
  376. Gets information about package foo from the repos or the AUR.
  377.  
  378. yay -S foo --mflags "--skipchecksums --skippgpcheck"
  379. Installs foo while skipping checksums and pgp checks.
  380.  
  381. yay --devel --save
  382. Sets devel to true in the config.
  383.  
  384. yay -P --stats
  385. Shows statistics for installed packages and system health.
  386.  
  387. pacman -Qmq | grep -Ee '-(cvs|svn|git|hg|bzr|darcs)$' | yay -S --needed -
  388. pacaur-like devel check.
  389.  
  390. FILES
  391. CONFIG DIRECTORY
  392. The config directory is $XDG_CONFIG_HOME/yay/. If $XDG_CONFIG_HOME is unset, the config directory will fall
  393. back to $HOME/.config/yay.
  394.  
  395. config.json Is used to store all of Yay's config options. Editing this file should be done through Yay,
  396. using the options mentioned in PERMANENT CONFIGURATION SETTINGS.
  397.  
  398. CACHE DIRECTORY
  399. The cache directory is $XDG_CACHE_HOME/yay/. If $XDG_CACHE_HOME is unset, the cache directory will fall back
  400. to $HOME/.cache/yay.
  401.  
  402. completion.cache holds a list of of all packages, including the AUR, for shell completion. By default the
  403. completion files are refreshed every 7 days.
  404.  
  405. vcs.json tracks VCS packages and the latest commit of each source. If any of these commits change the
  406. package will be upgraded during a devel update.
  407.  
  408. BUILD DIRECTORY
  409. Unless otherwise set this should be the same as CACHE DIRECTORY. This directory is used to store downloaded
  410. AUR Packages as well as any source files and built packages from those packages.
  411.  
  412. PACMAN.CONF
  413. Yay uses Pacman's config file to set certain pacman options either through go-alpm or Yay itself. Options
  414. inherited include most libalpm options and pacman options.
  415.  
  416. Notably: Databases, Color and *Path/*Dir options are used.
  417.  
  418. SEE ALSO
  419. makepkg(8), makepkg.conf(5), PKGBUILD(5), pacman(8), pacman.conf(5)
  420.  
  421. See the arch wiki at https://wiki.archlinux.org/index.php/Arch_User_Repository for more info on the AUR.
  422.  
  423. BUGS
  424. Please report bugs to our GitHub page https://github.com/Jguer/yay
  425.  
  426. AUTHORS
  427.  
  428. Yay v8.972+ 2018-07-01 YAY(8)
Advertisement
Add Comment
Please, Sign In to add comment