68
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 May 2026
68 points (100.0% liked)
Linux
13785 readers
445 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
Been using Void for a while now, at home and at work, about 4 installs in total.
I have my own packages repo which follows the official void-packages closely where I keep my custom templates, they get built by CI and signed, so on my void machines I simply add my repo to xbps config and get all my junk. Here's the repo: https://code.hosaka.cc/hosaka/vast-packages
In addition, I rsync the official repo to mirror it on my server that syncs every few hours and my custom packages are build against that (see the CI workflow in the repo). This also has a benefit of being able to update the packages on my machines from my own mirror at much faster speeds.
It took me a while to get things setup this way, but was worth it in the end.
Besides speed, why would I want my own package repo?
What are your "custom templates" and "all my junk"?
Packages that cannot be accepted upstream: themes, icons, fonts, packages that are "too new" (think Zig 0.16 for example), anything that packages binary blobs, anything that maintainers refuse to accept like Brave browser, or even your own tools.
Just off the top of my head. The reason I started that repo in the first place was to get a Noctalia package that I can install across multiple machines.