Jo

the `--upgrademenu` flag is just dangling currently and I think it can be unified with `--combinedupgrade`. It's true `yay -Su` is not taking care of either `--nocombinedupgrade --noupgrademenu` Currently these...

`-x` is used for `--regex` in `-F`, although it's still available for `-S` and regex is behind `--search`/`-s` it might be confusing if you already associate with regex.

Actually a good point but instead of `noaur` there's a `-n` in query options that applies well ``` -n, --native Restrict or filter output to packages that are found in...

I'm guessing this is using `yay -Syuu`. Before yay 12 `-uu` was ignored for AUR packages. yay now respects the downgrade instructions. reference pacman man page for -u --sysupgrade: >Pass...

> .e.g https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD doesn't seem to show anything @marcin-rzeznicki Yay does not execute PKGBUILD functions when checking for updates, only the `.SRCINFO` (RPC information, not locally EDIT: this was already...

yay uses both `XDG_CACHE_HOME` and `HOME`, otherwise it defaults to a tmpdir ```go func getCacheHome() (string, error) { uid := os.Geteuid() if cacheHome := os.Getenv("XDG_CACHE_HOME"); cacheHome != "" && uid...

I can reproduce this by setting `config.json` to ```json { "buildDir": "/yay" } ``` why it gets set to that is my question

I'm guessing this is due to the division of source gathering and install but would appreciate someone to try it out

In the old engine yay would install those packages nonetheless but not properly warn you about it. Maybe `14 Packages to upgrade.` -> `14 Packages to install/upgrade`. And adding a...

Hey @Porkepix, the new engine only uses "batch install", meaning it will build all AUR packages and then installs them in one go. > Notice the new confirmation as compared...