Void User Packages
VUP is an unofficial Void Linux user repository. It keeps package work close to xbps-src: source templates are built in CI, release assets are exposed as XBPS repositories, and the website indexes what is available for each architecture.
The project is separate from Void Linux and does not try to replace XBPS, xbps-src, or the official repositories. It is plain repository plumbing for people who want binaries without maintaining a pile of fragile scripts.
XBPS repository
Install VUP helper
Adds the GitHub-hosted VUP repository for the selected architecture and installs vuru, the helper used by the package pages.
sudo xbps-install -R https://github.com/VUP-Linux/vup/releases/download/core-x86_64-current -S vuru- arch
- channel
- current
- source
- releases
Using VUP
VUP packages are distributed as plain XBPS repositories. You can add them with xbps-install directly, or use vuru, a small helper that keeps the common operations short and searches VUP alongside the official Void repositories.
Every package page lists the raw XBPS commands as well, for users who prefer not to install another tool.
Search
Run vuru search <term> to look up packages across VUP and the official Void repositories in a single query. Results include the source repository so it is clear where each binary comes from.
Install
vuru install <package> resolves the package against the configured repositories and installs the matching prebuilt binary. There are no long release URLs to copy around.
Update
vuru install -Su synchronises the repositories and updates every installed package, exactly like xbps-install -Su would.
Latest Updates
View all packagesVoid-shaped repository
Templates follow Void packaging conventions and build into ordinary .xbps packages instead of a separate package format.
Release-backed repos
GitHub release assets act as XBPS repositories, so there is no custom package server that has to stay alive.
Categorized templates
Packages live under category directories, with tooling resolving templates, files, patches, and triggers from that layout.
Changed packages only
CI rebuilds the templates affected by a change, so adding packages does not require rebuilding the whole repository.
Packages and source
Package pages provide architecture-aware install commands and source/template views, not just a flat download index.
Builds are not review
If a template builds, it can be accepted. Users should inspect templates before installing software from third-party contributors.
