Personal Arch Linux PKGBUILDs — modified, improved and new packages I use.
I also use this repo to get hands-on with Copilot/AI workflows and learn agentic coding in practice.
Add one of these to your paru.conf (usually ~/.config/paru/paru.conf or /etc/paru.conf):
All packages:
[olwig/pkgbuilds]
Url = https://github.com/olwig/pkgbuilds
Depth = 3Just grok-build:
[olwig/pkgbuilds-grok-build]
Url = https://github.com/olwig/pkgbuilds
Path = packages/grok-buildThen run:
paru -SyaAfterwards you can install packages from this repo with paru -S <pkgname>.
Package directories live under packages/.
⚠️ grok-build These packages install Grok on the host. If you are also paranoid about running Grok on your host, use the externally sandboxed Docker/Podman image instead: olwig/grok-build-boxed.Sandboxing should not sit inside grok-build. grok-build is what you want contained; relying on its own built-in sandbox to isolate itself fights that goal. An outer shell is better — one that is not maintained by the very thing it is meant to protect against.
-
Root (workflows, scripts, actions, etc.) → MIT
See theLICENSEfile in the root. -
Each package folder → 0BSD (as prescribed by Arch Linux for PKGBUILDs)
Every package folder contains its ownLICENSEfile.