README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
# Yay
2018-02-17 18:25:43 +00:00
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
Yet Another Yogurt - An AUR Helper Written in Go
2016-10-05 01:11:10 +00:00
2017-08-05 01:15:12 +00:00
#### Packages
2018-02-17 18:25:43 +00:00
2020-07-04 19:31:51 +00:00
[![yay ](https://img.shields.io/aur/version/yay?color=1793d1&label=yay&logo=arch-linux&style=for-the-badge )](https://aur.archlinux.org/packages/yay/)
[![yay-bin ](https://img.shields.io/aur/version/yay-bin?color=1793d1&label=yay-bin&logo=arch-linux&style=for-the-badge )](https://aur.archlinux.org/packages/yay-bin/)
[![yay-git ](https://img.shields.io/aur/version/yay-git?color=1793d1&label=yay-git&logo=arch-linux&style=for-the-badge )](https://aur.archlinux.org/packages/yay-git/)
![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)
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
## Objectives
2016-10-05 01:11:10 +00:00
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.
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
Yay is based on the design of [yaourt ](https://github.com/archlinuxfr/yaourt ), [apacman ](https://github.com/oshazard/apacman ) and [pacaur ](https://github.com/rmarquis/pacaur ). It is developed with these objectives in mind:
2016-10-05 01:11:10 +00:00
2019-04-03 22:06:22 +00:00
- Provide an interface for pacman
- Yaourt-style interactive search/install
- Minimal dependencies
- Minimize user input
- Know when git packages are due for upgrades
2016-12-10 00:12:09 +00:00
2017-04-17 13:03:47 +00:00
## Features
2018-02-17 18:25:43 +00:00
2019-04-03 22:06:22 +00:00
- 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
2016-12-16 02:34:04 +00:00
2018-05-11 02:59:41 +00:00
## Installation
2018-03-01 16:13:46 +00:00
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
If you are migrating from another AUR helper, you can simply install Yay with that helper.
2018-05-11 02:59:41 +00:00
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
Alternatively, the initial installation of Yay can be done by cloning the PKGBUILD and
building with makepkg:
2019-04-03 22:06:22 +00:00
2018-05-11 02:59:41 +00:00
```sh
git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si
```
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
## 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
2018-06-04 18:22:16 +00:00
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
#### Yay does not display colored output. How do I fix it?
2019-04-03 22:06:22 +00:00
Make sure you have the `Color` option in your `/etc/pacman.conf`
(see issue [#123 ](https://github.com/Jguer/yay/issues/123 )).
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
#### Yay is not prompting to skip packages during system upgrade.
2019-04-03 22:06:22 +00:00
The default behavior was changed after
[v8.918 ](https://github.com/Jguer/yay/releases/tag/v8.918 )
(see [3bdb534 ](https://github.com/Jguer/yay/commit/3bdb5343218d99d40f8a449b887348611f6bdbfc )
and issue [#554 ](https://github.com/Jguer/yay/issues/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 ](https://wiki.archlinux.org/index.php/System_maintenance#Partial_upgrades_are_unsupported ).
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
#### Sometimes diffs are printed to the terminal, and other times they are paged via less. How do I fix this?
2019-04-03 22:06:22 +00:00
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`).
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
#### Yay is not asking me to edit PKGBUILDS, and I don't like the diff menu! What can I do?
2019-04-03 22:06:22 +00:00
`yay --editmenu --nodiffmenu --save`
2018-06-19 09:13:56 +00:00
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
#### How can I tell Yay to act only on AUR packages, or only on repo packages?
2019-04-03 22:06:22 +00:00
`yay -{OPERATION} --aur`
`yay -{OPERATION} --repo`
2018-06-19 09:13:56 +00:00
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
#### An `Out Of Date AUR Packages` message is displayed. Why doesn't Yay update them?
2019-04-03 22:06:22 +00:00
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 )).
2018-07-17 14:49:47 +00:00
README grammar, spelling, rewording, organizing (#661)
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
2018-08-30 09:54:16 +00:00
#### Yay doesn't install dependencies added to a PKGBUILD during installation.
2019-04-03 22:06:22 +00:00
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.
2018-07-19 16:38:41 +00:00
2018-12-06 22:36:53 +00:00
#### I know my `-git` package has updates but yay doesn't offer to update it
2019-04-03 22:06:22 +00:00
2018-12-06 22:36:53 +00:00
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.
2019-04-03 22:06:22 +00:00
#### I want to help out!
Check `CONTRIBUTING.md` for more information.
2018-05-11 02:59:41 +00:00
## Examples of Custom Operations
2020-02-29 17:53:58 +00:00
| 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. |
2017-04-17 13:03:47 +00:00
2018-05-11 02:59:41 +00:00
## Images
2019-04-05 17:00:48 +00:00
< p float = "left" >
< img src = "https://rawcdn.githack.com/Jguer/jguer.github.io/77647f396cb7156fd32e30970dbeaf6d6dc7f983/yay/yay.png" width = "42%" / >
< img src = "https://rawcdn.githack.com/Jguer/jguer.github.io/77647f396cb7156fd32e30970dbeaf6d6dc7f983/yay/yay-s.png" width = "42%" / >
< / p >
< p float = "left" >
2020-07-10 22:52:02 +00:00
< img src = "https://rawcdn.githack.com/Jguer/jguer.github.io/77647f396cb7156fd32e30970dbeaf6d6dc7f983/yay/yay-y.png" width = "42%" / >
< img src = "https://rawcdn.githack.com/Jguer/jguer.github.io/77647f396cb7156fd32e30970dbeaf6d6dc7f983/yay/yay-ps.png" width = "42%" / >
2019-04-05 17:00:48 +00:00
< / p >