Yay - diffs to show?

what does "diffs to show ? means ? what should i type to download the app ?

 Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)


[endea-andrew@endea-msi ~]$ yay -S brightness-controller-git
:: Checking for conflicts...
:: Checking for inner conflicts...
[Repo:10]  python-shiboken2-5.15.0-2  pyside2-5.15.0-2  python-cx_freeze-6.2-1  qt5-charts-5.15.0-1  qt5-xmlpatterns-5.15.0-1  qt5-remoteobjects-5.15.0-1  qt5-websockets-5.15.0-1  qt5-datavis3d-5.15.0-1  assimp-5.0.1-2  qt5-3d-5.15.0-1
[Aur:1]  brightness-controller-git-2.3.1-3

:: Downloaded PKGBUILD (1/1): brightness-controller-git
  1 brightness-controller-git        (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>

These are posts worth reading about it:

TL;DR: When installing software from the AUR, you should get in a habit of inspecting PKGBUILD files, and yay has this nice utility where, upon updates, it only shows you the differences in the PKGBUILD, so you can quickly see what changed.

3 Likes

how to do that ? let yay update of package diff when update.

thx

yay --diffmenu --save

Although it appears to already be turned on from your output above.

@dalto
can you pls explain to me what option should i enter for the yay prompt below ?
i wanted to download brightness controller git…
hence i should enter “1” , right ?
how about diffs to show ? what should i do about it ? it is the option that show me the different in package right ? should should i enter with regarding to that ?

is there lesson or youtube that teaches how to “inspect pkgbuild” as in the post above ?

Type N to show nothing (only do this if you trust the package), A to show differences/PKGBUILD files for all packages you’re building, I to show them only for the packages that are already installed and No to show the differences for packages that are not yet installed. Or you can type the number of package for which you want to see the PKGBUILD file or differences…

This is just for your convenience so you can inspect the PKGBUILD files without having to visit aur.archlinux.org.

I recommend following the Arch wiki and building at least one package manually, by the book, before using an AUR helper like yay. Just so you understand what’s going on.

It’s a bit overwhelming to jump straight in and that’s why most users just ignore this and willy-nilly install stuff from the AUR. If you want to do this properly, you should try to understand the Arch package build process, and for that you need to read the wiki. If you have any specific questions, I and many others will be happy to answer.

4 Likes