mirrors/yay
1
0
Fork 0
mirror of https://github.com/Jguer/yay.git synced 2025-12-27 05:15:42 -05:00
Code Issues Packages Projects Releases Wiki Activity

Correct capitalization of 'Yay' in README.md (#2748)

Browse Source 
* Correct capitalization of 'Yay' in README.md

* Update README to use lowercase 'yay'
This commit is contained in:
Aarik Pokras
2025-12-22 17:20:27 -05:00
committed by GitHub
parent 15c0597562
commit 95262efc83
1 changed files with 15 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
README.md
View File

@@ -4,7 +4,7 @@
![AUR votes](https://img.shields.io/aur/votes/yay?color=333333&style=for-the-badge)
[![GitHub license](https://img.shields.io/github/license/jguer/yay?color=333333&style=for-the-badge)](https://github.com/Jguer/yay/blob/master/LICENSE)
# Yay
# yay
Yet Another Yogurt - An AUR Helper Written in Go
@@ -28,14 +28,14 @@ Yet Another Yogurt - An AUR Helper Written in Go
## Installation
If you are migrating from another AUR helper, you can simply install Yay with that helper.
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.
> 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
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.
@@ -79,7 +79,7 @@ you can simply install yay using pacman (as root):
```sh
pacman -S --needed git base-devel yay
```
> [!WARNING]
> [!WARNING]
> distributions sometimes lag updating yay on their repositories.
## First Use
@@ -115,42 +115,42 @@ pacman -S --needed git base-devel yay
## Frequently Asked Questions
- **Yay does not display colored output. How do I fix it?**
- **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](https://github.com/Jguer/yay/issues/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
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 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?**
- **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?**
- **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 `PKGBUILD`s
(see [outdated AUR packages](https://wiki.archlinux.org/index.php/Arch_User_Repository#Foo_in_the_AUR_is_outdated.3B_what_should_I_do.3F)).
- **Yay doesn't install dependencies added to a PKGBUILD during installation.**
- **yay doesn't install dependencies added to a PKGBUILD during installation.**
Yay resolves all dependencies ahead of time. You are free to edit the
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`.
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!**
@@ -159,7 +159,7 @@ pacman -S --needed git base-devel yay
## Support
All support related to Yay should be requested via GitHub issues. Since Yay is not
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.
@@ -167,7 +167,7 @@ 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
other relevant information. Never make reports using yay or any other external
tools.
## Images