I've avoided actually learning this for too long!
Here are some notes from my first experience with touching a PKGBUILD and rebuilding on purpose.
Specifically, I was trying to solve the bluez-git/bluez-lib conflict.
This was made much easier with some googling:
The comment on the `bluez-git` aur package, which linked to the below commit:
https://aur.archlinux.org/packages/bluez-git/#comment-792471
Not sure what this is a diff for... but I think it's the main bluez pkgbuild:
https://github.com/archlinux/svntogit-packages/commit/8932012438c328ca7641c9ee8625fea59d21d870
Arch forums, someone with the same issue, including a recommendation for how to edit the bluez-git PKGBUILD https://bbs.archlinux.org/viewtopic.php?id=264070. This guy however, did not have the rest of the picture, which I got in the next link.
Some yay explanation/options here... https://github.com/Jguer/yay/issues/750
The edit and rebuild process:
yay -G
bluez-git
- this creates a
bluez-git dir in your cwdcd
bluez-git
makepkg
-si
in the bluez-git
dir> My impression is that this is roughly what yay
and other pacman tools do > anyway - clone some repo into a
dir and run makepkg
-si
in it, assuming the >
repo has a well constructed PKGBUILD.
The above built ok, and i was able to
yay -Syu
afterwards.
> Or, as i learned, just
yay
, which does a
non-interactive -Syu by default. > Thanks, man
page!
Haven't gotten back around to be sure that bluez/bluetooth is actually still working.... will confirm at some point.