1. Don't use this repo if you don't know what you are doing. It may break your great voidlinux experience
2. I won't upstream this as some packages here may break [requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements) like git repo has no tags or package may be cutom kernel.
3. If you want to upstream, go ahead but don't engage me -> You maintain. Although You can reference as working example.
4. Builds here will be only **glibc-x86-64** for now, altough I may consider other variants if you donate me every month
5. I may rename/remove package without prior notification.
# Why
## To maintain own repo
Official repo is good quality for desktop usage however:
- Sometimes your PR is stale for long time
- According to guidelines they won't include some specific forks
- You want some feature needed mostly by you
- Some packages are not released
- I don't use flatpak for personal reason (mostly size of packages and sdks based mostly on ubuntu I don't really like)
- Instead flatpaks I use AppImages that are not so easy to update in large quantity
- Void toolchains are up-to-date
## To use repo actions for builds
- It's easy to maintain
- Public build logs are more trustowrthy
- Clear and simple repo structure similar to official one
# Builds
- Built on docker with actions on this repo
- Signed with private key
- Triggered on push to release branch
- Release branch always compile
- New packages tested on other branches
## How does it work
1. Set up void docker container, instal needed tools
2. Checkout to some x dir
3. Replace dir "srcpkgs" from official github to one from this repo
4. Iterate over its dirs and trigger `./xbps-src pkg`
5. If all succeed, will mount remote path on server
6. Remove all packages there, clean index
7. Upload packages
8. Update index and sign packages with ITmodulo privkey
# LICENSE
Actions workflow file and template files are licensed under BSD-3-Clause-no-military
This should not impact the original source code licenses
