3 ms·
Nixpkgs experimented with a build environment based on uutils-coreutils instead of GNU coreutils[0]. A lot of bugs or unimplemented features were uncovered whic
by siraben 4y ago
Nixpkgs experimented with a build environment based on uutils-coreutils instead of GNU coreutils[0]. A lot of bugs or unimplemented features were uncovered which were fixed upstream and as a result software such as chromium, vim, emacs or even rustc itself builds properly now.[1] So it definitely could be a viable alternative in the future.
[0] https://github.com/NixOS/nixpkgs/pull/116274 https://github.com/NixOS/nixpkgs/pull/116274
[1] https://github.com/NixOS/nixpkgs/pull/116274#issuecomment-850950790 https://github.com/NixOS/nixpkgs/pull/116274#issuecomment-85...
- abathur 4y agoI'm always cautious about who I recommend Nix to, but I usually say that one of the best things waiting on the other side of the learning curve is what an incredible always-improving lever nix and nixpkgs can be for just about any task that involves or benefits from ~integrating a lot of software. But it's also hard to communicate what I mean by that without diving into a bunch of detail on some case where it proved useful to me. The ability to give uutils a shake at scale is a paragon. At some point I imagine it'll be able help ferret out a good fraction of remaining long-tail issues with oilshell's mostly-bash-compatible `osh` in short order.