Startseite Erkunden Hilfe
Anmelden
my
/
yay
1
0
Fork 0
Dateien Issues 0 Pull-Requests 0 Wiki

Keine Beschreibung

Struktur: 2f98d689c2
Branches Tags
yay
Viktor Drobot 2f98d689c2 Russian translation vor 4 Jahren
.github 2fa7b6ba3d fix(ci): use PAT so pipeline gets triggered vor 4 Jahren
completions fe091f7578 Fix typo in usage vor 5 Jahren
doc c6a17d02f4 Fix typos in man page vor 5 Jahren
pkg d003e96e07 fix(ci): fix env propagation vor 4 Jahren
po 2f98d689c2 Russian translation vor 4 Jahren
testdata 9795a36692 fix(yay): remove vendor and tweak ci vor 5 Jahren
.gitignore 0c45a390a2 fix(locale): make install with locale vor 4 Jahren
.golangci.yml d003e96e07 fix(ci): fix env propagation vor 4 Jahren
.pre-commit-config.yaml d003e96e07 fix(ci): fix env propagation vor 4 Jahren
Dockerfile 9795a36692 fix(yay): remove vendor and tweak ci vor 5 Jahren
LICENSE 59daf46714 Create LICENSE vor 8 Jahren
Makefile 2f98d689c2 Russian translation vor 4 Jahren
README.md 35475c7f4c fix(yay): lint README.md vor 5 Jahren
callbacks.go d4c327c153 fix(callbacks): fix callback extra \n vor 4 Jahren
clean.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
cmd.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
config.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
config_test.go d50ca0430b Enable testing in ci builds vor 5 Jahren
dep.go 9fccdcb30f fix(ci): implement stricter linting settings vor 5 Jahren
depCheck.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
depOrder.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
depPool.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
download.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
exec.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
go.mod d003e96e07 fix(ci): fix env propagation vor 4 Jahren
go.sum d003e96e07 fix(ci): fix env propagation vor 4 Jahren
install.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
keys.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
keys_test.go 9fccdcb30f fix(ci): implement stricter linting settings vor 5 Jahren
main.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
parser.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
print.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
query.go 1970dfa71b fix(query): fix package indexing on narrow search vor 4 Jahren
upgrade.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
upgrade_test.go 9fccdcb30f fix(ci): implement stricter linting settings vor 5 Jahren
utils.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
utils_test.go f2579f26a3 Move stringset to its own module vor 5 Jahren
vcs.go d003e96e07 fix(ci): fix env propagation vor 4 Jahren
vcs_test.go 9fccdcb30f fix(ci): implement stricter linting settings vor 5 Jahren

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