Linux

9642 readers

639 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

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

Experimenting with CachyOS kernel on NixOS via Chaotic's Nyx - NixOS Discourse (discourse.nixos.org)

submitted 1 week ago by ruffsl@programming.dev to c/linux@programming.dev

9 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] dinckelman@programming.dev 3 points 1 week ago (1 children)

My biggest issue with Nyx, and the reason why I've yanked it out of my flake twice now, is because unfortunately this repo has no quality control.

If the Nix foundation Hydra fails, the whole merge is cancelled. If Nyx' build system fails, they just write the broken packages into the equivalent of shit_that_broke.json, and still push it.

Given that I've only wanted to use 1 package from the entire repo, it is shocking that it's both impossible to bisect for debugging, but also increasingly frustrating to get any help with.

This is especially obvious for kernel packages, where nixos-unstable is a little behind Nyx, so fully expect your builds to error out frequently, if you use applications, reliant on specific kernel functions, like what openrgb/openrazer people experienced a few releases ago

[–] ruffsl@programming.dev 1 points 1 week ago

Appreciate the heads up. Looks like they use merge bots to auto update the package version JSON files for git packages, making for a very large/frequent commit history. Was that what made bisecting imposable?

I also see they pin the nixpkgs input, but do others normally modify that nixpkgs input to follow their global nixpkgs from their own system flake, or does that invalidate the use of Nyx community cache?