Explore >> Select a destination
|
You are here 
|
erikarow.land | ||
| | | | |
blog.thalheim.io
|
|
| | | | | No such file or directory: How I stopped worrying and started loving binaries on NixOS. In this article, I will discuss the technical issue of running pre-compiled executables on NixOS, and how we can improve the user experience by making these binaries work seamlessly using nix-ld. One of the key benefits of NixOS is its focus on purity and reproducibility. The operating system is designed to ensure that the system configuration and installed software are always in a known and predictable state. | |
| | | | |
fzakaria.com
|
|
| | | | | This is a write up of some discussion ongoing with some folks on the #nix-community IRC chat primarily being driven by Mic92. Nixpkgs maintains the highest rating on Repology for having the most packages & which are up to date. Unfortunately even with the current ecosystem of packages, there will always be gaps, and for beginners in NixOS a common question is: "I've download a binary and would like to run it on NixOS" Take a look at this graph https://repology.org/repositories/graphs Can we do better & s... | |
| | | | |
jakewharton.com
|
|
| | | | | ||
| | | | |
jmmv.dev
|
|
| | | In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?... | ||
