Nix Package Manager
Comments discuss Nix and NixOS as superior solutions for dependency management, reproducible builds, and avoiding conflicts with tools like pip, npm, and cargo, often recommending it over alternatives.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Nix is not "your own dependency management system"
Doesn't Nix ship its own version of every library dependency rather than using system libraries?
Assuming you're using only Nixpkg and not doing pip install, npm install, cargo install and so on like many people suggest and do.
You shouldn't need one. Use Nix instead, they did 99% of the work for you already.
can nixos/nix package manager be somehow related?
I would really like to know how NixOS solves this problem for things like yarn, webpack, parcel, esbuild, npm, pip, conda, cargo, stack, go modules, ruby gems, etc.
You may want to consider using Nix, with nix flakes.
NixOS already did this at https://github.com/NixOS/nixpkgs/issues/74516
How is it different from Nix? Hell, it is much more easier/flexible with Nix, just clone nixpkgs and update a few files and build from that. You can have as many versions as you want.
Does nix and flakes help with a reproducible build environment?