I still don’t think I fully agree, or at least it seems weird to me.
pacman -U is the supported way to build and install AUR packages on Arch, and anyway that’s what a AUR helper like
paru would be doing behind the scenes when it installs
I guess I see a few use-cases here, with your documentation somewhere in an awkward middle spot:
- I just want to use 5.99 on Arch/Manjaro, in which case I would install
kicad-git or more likely
kicad-nightly from AUR [your statement addresses this]. In this case I would use
yay, or bare
makepkg to build the package followed by
pacman to install it.
- I want to install a specific commit, or a patched build. In this case I would start following your instructions but then diverge: I would customize the PKGBUILD with the specific commit and/or patches necessary, then run
pacman to build and install my customized build.
- I’m developing kicad, in which case I just want a development build environment but I don’t want to install my builds. In this case I would just do a clone of the git repository from gitlab and set up the CMAKE flags myself. I have to make sure all the dependencies are installed, but that’s done already if I’ve done option 1 above (or probably even if I’ve installed the prebuilt kicad 5.1 package – Arch doesn’t have separate
-dev packages like many other distributions).
So I guess it just seems weird to me to start to build a package but then not get any of the advantages of the package manager That said, I understand that it’s a relatively easy way to ensure the build environment is setup correctly, so maybe that makes sense for people getting started with doing their own builds. It’s just not the way I would do it.
Edit: actually thinking about it more, I would not have thought to do it this way but I kind of like it as a way to make sure your build environment is set up correctly. “the easy way” like you say. Kudos