PKGBUILDs in the AUR that I maintain
- Shell 90.6%
- Jsonnet 5.3%
- Lua 2.5%
- Just 1.6%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
|
||
| .crow | ||
| _scripts | ||
| alpm-html | ||
| alpm-reboot-required | ||
| cowsay-color-patch | ||
| formatjson5 | ||
| ktermlaunch | ||
| kubecolor | ||
| LICENSES | ||
| nvim-treesitter-parsers-git | ||
| runrestic | ||
| scrutiny | ||
| scrutiny-web-frontend | ||
| sonobuoy | ||
| wait4tailscale | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| Justfile | ||
| LICENSE | ||
| README.md | ||
| renovate.json | ||
| renovate.json.license | ||
The various packages I help maintain in the AUR
See the list in the AUR directly.
This repo uses the aurpublish package by Eli Schwartz. Big thanks, it really makes it easy!
It also uses nvchecker to check if all of these packages are up-to-date. To do so:
nvchecker -c nvcheck.toml
nvcmp -c nvcheck.toml
(... update PKGBUILD files ...)
nvtake -c nvcheck.toml --all # when they are all updated
Make sure you run aurpublish setup after cloning this repo on a new machine in order to set up the git hooks.
This repo has CI/CD set up so all you need to do is push, it will automatically publish.
Importing a package
If you've taken over maintenance for a package, you can bring it into the repo by running aurpublish -p PACKAGE.