Vision

Build your system, become independent.

Aren't you tired of enshittification?
You don't have to deal with proprietary products; the solution is not to play their game.

1. You can physically own your programs and have them pre-configured; your time is saved and respected.
2. You can pick specific versions of packages and have them be the same forever; everything¹ is open source.
3. You can have a system that always serves you; changing things or updating programs are choices.

Total control, you don't even depend on repositories ², but you can use them if you want to.

.
├── build/ # your resulting iso.
├── build.sh # build script.
├── pkgs.d # packages to be included.
└── root # mounted '/' directory.

Build

1. Create variables in pkgs.d/* such as $system containing the packages you want.
2. Make sure these are included in the build script (e.g. -p "$system $drivers $wayland $kde").
3. Add (configuration or not) files in the root folder (this will be mounted at / on the resulting system).
4. Pull in the void-mklive submodule with git submodule update --init --remote.
5. Run bash build.sh, and the resulting .iso will be in ./build!

Tip

You might want to look into void-mklive to understand what the various flags do.
Additionally, it is possible to stop at the rootfs, instead of building a full bootable ISO.

Switch to the amd, nvidia or intel (depending on your card) branch for a selection of graphics drivers.
This repository contains the absolute barebones; if you want the same thing but with a display server, audio, and bluetooth already set up, please use the vision-xorg or vision-wayland fork instead.
Once you've played around enough, I recommend forking vision to be able to fetch changes³.

Warning

Make sure to include the microcode for your CPU (e.g. linux-firmware-amd or intel-ucode) and the additional firmware required by your hardware (e.g. linux-firmware-network).

Time to name your own Void Linux fork!
This could be done on any other distro or from scratch, but they make it really comfy to do so.
Read the Void Handbook⁴ and browse Void Packages⁵.

Note

Use the vision tag (if your fork isn't private and on GitHub) to allow discoverability by others.
Exited to see all your beautiful r/unixporn-type setups easily installable and ready to use.
I have Sway and KDE Plasma on Wayland installed and of course, configured exactly to my liking!

Install

Run void-installer (this will get it done very fast) or do it manually.

Footnotes

1. Excluding some hardware binary blobs, use/make better hardware to avoid this! ↩

2. You can add void-packages as a submodule so that even if Void (going strong since 2008) repositories ever go down and there's not a single mirror available, you can still have everything exactly the way it was; you'll be pulling from upstream and building things yourself. ↩

3. Very rare and if there ever are they'll be changes/additions to the drivers selection in order to support new hardware. ↩

4. You can add void-docs to include system documentation locally. ↩

5. Refer to the InfraDocs if you're curious about how Void Linux runs things; maybe you want to host your own mirror. ↩