Без опису

jguer d0450179f9 fix(usecolor): usecolor belongs to text. remove deprecated 4 роки тому
.github 2fa7b6ba3d fix(ci): use PAT so pipeline gets triggered 4 роки тому
completions fe091f7578 Fix typo in usage 5 роки тому
doc c6a17d02f4 Fix typos in man page 5 роки тому
pkg d0450179f9 fix(usecolor): usecolor belongs to text. remove deprecated 4 роки тому
po 9d93a1f1bd fix mostly br terms to pt 4 роки тому
testdata 9795a36692 fix(yay): remove vendor and tweak ci 5 роки тому
.gitignore 0c45a390a2 fix(locale): make install with locale 4 роки тому
.golangci.yml d003e96e07 fix(ci): fix env propagation 4 роки тому
.pre-commit-config.yaml d003e96e07 fix(ci): fix env propagation 4 роки тому
Dockerfile 9795a36692 fix(yay): remove vendor and tweak ci 5 роки тому
LICENSE 59daf46714 Create LICENSE 8 роки тому
Makefile 0548d86dea Merge branch 'next' into yay-ptBR 4 роки тому
README.md 35475c7f4c fix(yay): lint README.md 5 роки тому
callbacks.go d4c327c153 fix(callbacks): fix callback extra \n 4 роки тому
clean.go d003e96e07 fix(ci): fix env propagation 4 роки тому
cmd.go d003e96e07 fix(ci): fix env propagation 4 роки тому
config.go d0450179f9 fix(usecolor): usecolor belongs to text. remove deprecated 4 роки тому
config_test.go d50ca0430b Enable testing in ci builds 5 роки тому
dep.go 9fccdcb30f fix(ci): implement stricter linting settings 5 роки тому
depCheck.go d003e96e07 fix(ci): fix env propagation 4 роки тому
depOrder.go d003e96e07 fix(ci): fix env propagation 4 роки тому
depPool.go d003e96e07 fix(ci): fix env propagation 4 роки тому
download.go d003e96e07 fix(ci): fix env propagation 4 роки тому
exec.go d003e96e07 fix(ci): fix env propagation 4 роки тому
go.mod d003e96e07 fix(ci): fix env propagation 4 роки тому
go.sum d003e96e07 fix(ci): fix env propagation 4 роки тому
install.go d0450179f9 fix(usecolor): usecolor belongs to text. remove deprecated 4 роки тому
keys.go d003e96e07 fix(ci): fix env propagation 4 роки тому
keys_test.go 9fccdcb30f fix(ci): implement stricter linting settings 5 роки тому
main.go d0450179f9 fix(usecolor): usecolor belongs to text. remove deprecated 4 роки тому
parser.go d003e96e07 fix(ci): fix env propagation 4 роки тому
print.go d0450179f9 fix(usecolor): usecolor belongs to text. remove deprecated 4 роки тому
query.go 1970dfa71b fix(query): fix package indexing on narrow search 4 роки тому
upgrade.go d003e96e07 fix(ci): fix env propagation 4 роки тому
upgrade_test.go d0450179f9 fix(usecolor): usecolor belongs to text. remove deprecated 4 роки тому
utils.go d003e96e07 fix(ci): fix env propagation 4 роки тому
utils_test.go f2579f26a3 Move stringset to its own module 5 роки тому
vcs.go d003e96e07 fix(ci): fix env propagation 4 роки тому
vcs_test.go 9fccdcb30f fix(ci): implement stricter linting settings 5 роки тому

README.md

Yay

Yet Another Yogurt - An AUR Helper Written in Go

Packages

yay yay-bin yay-git GitHub license

Objectives

There's a point in everyone's life when you feel the need to write an AUR helper because there are only about 20 of them. So say hi to 20+1.

Yay is based on the design of yaourt, apacman and pacaur. It is developed with these objectives in mind:

  • Provide an interface for pacman
  • Yaourt-style interactive search/install
  • Minimal dependencies
  • Minimize user input
  • Know when git packages are due for upgrades

Features

  • Perform advanced dependency solving
  • Download PKGBUILDs from ABS or AUR
  • Tab-complete the AUR
  • Query user up-front for all input (prior to starting builds)
  • Narrow search terms (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
  • Run without sourcing PKGBUILD

Installation

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

Alternatively, the initial installation of Yay can be done by cloning the PKGBUILD and building with makepkg:

git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si

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.

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).

Yay is not prompting to skip packages during system upgrade.

The default behavior was changed after v8.918 (see 3bdb534 and issue #554). To restore the package-skip behavior use --combinedupgrade (make it permanent by appending --save). Note: skipping packages will leave your system in a partially-upgraded state.

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 --nodiffmenu --save

How can I tell Yay to act only on AUR packages, or only on repo packages?

yay -{OPERATION} --aur yay -{OPERATION} --repo

An 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 an 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.

Examples of Custom Operations

Command Description
yay <Search Term> Present package-installation selection menu.
yay -Ps Print system statistics.
yay -Yc Clean unneeded dependencies.
yay -G <AUR Package> Download PKGBUILD from ABS or AUR.
yay -Y --gendb Generate development package database used for devel update.
yay -Syu --devel --timeupdate Perform system upgrade, but also check for development package updates and use PKGBUILD modification time (not version number) to determine update.

Images