deleted by creator
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?
Why? You could just diff and build for yourself. This is a bit unhinged…
I wasn’t sure if these results were specific to my older hardware, or more generalizable to newer systems.
Wait…what? If anything, building on your current hardware would yield more realistic results.
What exactly did you do here, just swap packages?
I don’t have resources to locally build an optimized kennel for every update for each of my systems, thus my interests in keeping with a community cache.
I didn’t do much here, just swapped the kernel via config and ran some benchmarks. I posted as I was more curious to hear of what engineering trade offs may be at play, and what experience folks have had in daily driving CatchyOS’s kernel patch sets.
You…just run commands. What resources are you talking about? It’s a one liner.
Compiling the Linux kernel from scratch takes over an hour on this laptop. Given I’m tracking the unstable channel on a rolling distro means doing that several times a week. Ain’t nobody got time for that. Or at least I don’t…
“I was so focused on whether I could, I didn’t stop to consider whether I should.” —inventor of the Steam Brick
