- Shell 98.7%
- HTML 1.3%
| pkg | ||
| www | ||
| .gitignore | ||
| bar.pub.github.gpg | ||
| bar.pub.gpg | ||
| README.md | ||
| repo-add.sh | ||
| repo-update.sh | ||
BAR - https://bar.budlabs.xyz
Buds Arch Repositories
I used to maintain packages for my own programs on AUR, now I host them here instead, pre-compiled and packaged. I also added some packages found on AUR that are dependencies to my own. Other packages in the BAR are either not in AUR or had broken packages on AUR.
curl -s https://bar.budlabs.xyz/bar.pub.gpg | sudo pacman-key --add -
sudo pacman-key --lsign-key A181CCE78A37E1CDF2438198A29E3FAA7327E469
if ! grep -q "\[BAR\]" /etc/pacman.conf; then
cat <<-'EOB'
[BAR]
Server = https://bar.budlabs.xyz
SigLevel = Required DatabaseOptional
EOB
fi | sudo tee -a /etc/pacman.conf
sudo pacman -Sy
How it works
repo-update.sh builds all packages and add them to a .gitignored directory called "repo". We then create BAR.db in the repo directory and copy contents of "www" and bar.pub.gpg to "repo", and push repo dir to budlabs.xyz .
So as of now everything is in a flattened directory structure
which is quite messy, but i wanted it so that the Server line in pacman.conf
would read: https://bar.budlabs.xyz , and i couldn't figure out how to achieve
it without a flat directory. It also doesn't matter that much,
i figured that if i in the future want a more complex frontend
i can have: repo/index.html and repo/www/ or something..
Maybe i will do some redirect trickery in the server config, but that means the server configuration becomes a dependency for the BAR repository...