nix.dev VS main

Nix (https://nix.dev/) can provide all of this, although in a smarter way than just through dumping everything in the VCS. Some projects use it already to provide a reproducible development environment and if done right a clean build is just a `nix-build` away.

Author doesn’t mention it but I wonder if tried or considered Nix/NixOS’s reproducible developer environments and ruled them out for any reason. I couldn’t tell from the article if there’s something unique to his requirements that disqualifies them.

https://nixos.org/explore

https://nix.dev/

if you want something a more in-depth, zero to nix is a great resource for all things nix (they have a section dedicated to flakes here, but i would pay attention to the notice at the top about reading some other things first), along with nix.dev, and of course, the nixos wiki article on flakes

On nix.dev it say I would need to cross compile to make it work, is there some way in which i can build natively on my machine.

Hey

Cachix founder here. Here are a few links for getting started:

- https://nix.dev Nix tutorials

- https://devenv.sh Fast, Declarative, Reproducible, and Composable Developer Environments

Let me know if you have any questions. Domen

Nix pills and nix.dev are my favorites, alongside the official documentation.

https://nix.dev/ is the best in depth resource I know but it's a work in progress.

For folks looking to understand why this is so https://nix.dev and https://devenv.sh/

Best place to start is to get rid of all the layered packages (RPMFusion) on top of the immutable image then swap to the ublue-Nvidia images that have all the codecs and Nvidia drivers built into the image itself.

If you're using Nvidia I'd recommend using Fedora Kinoite with the ublue-Nvidia image that comes with the Nvidia drivers pre-built in. That eliminates a big chunk of issues with their drivers which is just building the damn things. AMD and Intel drivers are built into the kernel and require zero effort.

What you are looking for is UBlue, https://github.com/ublue-os/main.

It's a variant of Silverblue with Nvidia drivers built in.

If you're using Nvidia, then install using the ublue Nvidia image which has the drivers built in, cause they can be a prick to manage otherwise.

What these sort of introductions to immutable always fail to consider is the other side of the coin, image-based. I'm working on https://universal-blue.org/ along with many people much more skilled than me. We build OCI container images on top of vanilla Fedora Silverblue & many other editions with different desktops. Those images can then be booted to (or rather rebased to) using rpm-ostree. This is a more robust way of extending the system than layering, and the same changes can be easily benefited or inherited from by anyone. You can even make your own image really easily!

I think that VanillaOS and SUSE are working on similar things, but we're not an OS project, just a downstream from Fedora. Fedora's full support is underway but with what's already working perfectly our methods are already IME some of the most robust and easy ways of delivering Nvidia drivers for example.

Download: https://github.com/ublue-os/main/releases/tag/v1.1.8