PRs welcome 🤗

• vOid Community repOsitory (oco)
• aka
• Void User Repository
• VUR
• testing repo
• waiting list
• void unstable

Providing:

• templates
• binaries
• by community
• for community

This project is not affiliated with or endorsed by the Void Linux project or its maintainers.
It is an unofficial community repository designed to simplify managing and building user-contributed packages using the void-packages build system.
Use at your own discretion.

A collection of template files for building packages on Void Linux.
If you dont wish to build the packages locally,
https://repo.osowoso.org repository provides prebuilt binaries.
Pick your architecture there and you will see

• Main repository with templates on Codeberg https://codeberg.org/oSoWoSo/oco
• mirror Github repository + CI https://github.com/oSoWoSo/Void_Community_Repository (Here we build binary packages)
• To make CI quicker we use daily updated Bootstrap Docker images from oco-builder
• nocross templates build support (GitHub aarch runner)
• Binary repository https://repo.osowoso.org/
• Just built (RSS feed) https://repo.osowoso.org/feed.xml

Browsers: It's waste of energy and when you finish building is maybe already new version out
We provide repackaged binaries, they all have -bin after
(You can use AppImages and manage them with AM, or flatpaks. They are usualy always latest)

in https://repo.osowoso.org/`(architecture)` are easy to understand READMEs Just pick your architecture

curl -fsSL "https://codeberg.org/oSoWoSo/oco/raw/branch/OCO/keys/oco-repo-key.plist" \
  -o /tmp/oco-repo-key.plist 2>/dev/null || \
curl -fsSL "https://raw.githubusercontent.com/oSoWoSo/Void_Community_Repository/OCO/keys/oco-repo-key.plist" \
  -o /tmp/oco-repo-key.plist
sudo cp /tmp/oco-repo-key.plist /var/db/xbps/keys/oco-repo-key.plist

Running ./ocoman -i will clone void-packages and oco into ~/void
PS: Destination could be changed look at ./ocoman -h

Clone Codeberg repo
git clone https://codeberg.org/oSoWoSo/oco
Copy srcpkgs directory to cloned void-packages

Then:

Use xnew <pkgname> to create new template
Fill everyhing as needed and remove rest
Use xlint <pkgname> to lint templates
Build templates with tests ./xbps-src -Q pkg <pkgname>
(Tests must be allowed in $XBPS_DISTDIR/etc/conf)
We build for x86_64 and aarch64 + musl variants
(I am usualy trying x86_64 and aarch64-musl crossbuild)
Add your changes
When you change any shlib from upstream void-packages, changes must be reflected in shlibs_remove and shlibe_append
When you add new shlib add it only to shlibe_append
After adding template, run ./ocoman -u to regenerate templates list and table
One commit per template, mesage: <pkgname> <version>

Create PR

• Manual
• Contributing
• Readme