Who needs documentation? The code is self-documenting! The entire thing’s on GitHub, just check the issues to figure out what’s going on! Didn’t work? Sorry, the thing got broke a few months ago. Just go through the commit history and I’m sure you’ll be up and running in no time!
I’ve also made a module that fixes your specific issue and uploaded it to my self hosted gitlab instance. The server is down right now? Well, isn’t that better? Now you can make the thing yourself! Remember to upload your thing to your GitHub, name it something like “nixos” and never mention it anywhere.
Who cares if it breaks? You can always just boot a previous generation! Need to rebuild without the breakage? You surely must now how to add a package from an earlier commit via flakes by now, right?
Just put my custom flake into your inputs! No, I won’t give ydu an example on how to integrate it into your config. The Flakes schema is an incredibly easy concept to grasp, after all. /s
Well, if you can’t figure out how to integrate the flake in 30 seconds by month 6, you clearly have a skill issue. Or a “sleeping at night instead of writing nix” issue. Better use a noob-friendly distro like arch.
Seriously though, despite all the flaws, there is no other packaging system where I can as painlessly use random forks of packages. I absolutely love how I’m able to run gnome-mobile on my x64 tablet. True to the NixOS way, I found the overlay on someone’s GitHub, there were only the files, no further instructions.
I also have a USB with live debian at all times, because you never know when you stumble upon a thing that just can’t work with NixOS
I really dig it as well, but hoo boy: the documentation still is… incredibly rough.
I’ve spent several evenings now trying to set up the development environment for a python package with additional binary file requirements (model weights) that I want to be included in the package.
It kinda works now with pyproject-nix, but I can’t manage to get an editable devshell running. And now it needs to unpack the requs everytime. 🙄
Beats contributing to the documentation/wiki. /s
Who needs documentation? The code is self-documenting! The entire thing’s on GitHub, just check the issues to figure out what’s going on! Didn’t work? Sorry, the thing got broke a few months ago. Just go through the commit history and I’m sure you’ll be up and running in no time!
I’ve also made a module that fixes your specific issue and uploaded it to my self hosted gitlab instance. The server is down right now? Well, isn’t that better? Now you can make the thing yourself! Remember to upload your thing to your GitHub, name it something like “nixos” and never mention it anywhere.
What do you mean the entire thing broke a few months ago? It broke only weeks ago, NixOS has the freshest breakages in the linux ecosystem
Who cares if it breaks? You can always just boot a previous generation! Need to rebuild without the breakage? You surely must now how to add a package from an earlier commit via flakes by now, right?
Just put my custom flake into your inputs! No, I won’t give ydu an example on how to integrate it into your config. The Flakes schema is an incredibly easy concept to grasp, after all. /s
You can vibe code your config so now you have no excuse
Well, if you can’t figure out how to integrate the flake in 30 seconds by month 6, you clearly have a skill issue. Or a “sleeping at night instead of writing nix” issue. Better use a noob-friendly distro like arch.
Seriously though, despite all the flaws, there is no other packaging system where I can as painlessly use random forks of packages. I absolutely love how I’m able to run gnome-mobile on my x64 tablet. True to the NixOS way, I found the overlay on someone’s GitHub, there were only the files, no further instructions.
I also have a USB with live debian at all times, because you never know when you stumble upon a thing that just can’t work with NixOS
I really dig it as well, but hoo boy: the documentation still is… incredibly rough.
I’ve spent several evenings now trying to set up the development environment for a python package with additional binary file requirements (model weights) that I want to be included in the package.
It kinda works now with pyproject-nix, but I can’t manage to get an editable devshell running. And now it needs to unpack the requs everytime. 🙄