3 ms·

>> Oh. Wait. There's literally no such way. > I think there is? There is no official way to do that. There's no history. There are no tools in nix to do that.

>> Oh. Wait. There's literally no such way. > I think there is? There is no official way to do that. There's no history. There are no tools in nix to do that. As you noted, you have to rely on the kindness of strangers to provide this service. Here's lazamar's own explanation why he built the tool: https://lazamar.github.io/download-specific-package-version-with-nix/ https://lazamar.github.io/download-specific-package-version-... Look at the beginning of the "automating" section to see what is required to do all that with nix. On top of that, in the entire discussion here exactly one person could actually show how to pin something to a version, so it's poorly documented, extremely complex and not really understood even for people who propose nix. > Now, with nvm, how could you guarantee that a particular version would not conflict with one the host OSs low-level libraries You probably don't, or stick it in a container somewhere. But this is about tradeoffs: does nix provide enough tradeoffs to use this complicated, complex and poorly documented system?

ducktective 5y ago
But the Nix way (how alien and complicated) is the theoretical sound way of handling dependencies. The docker solution is a blanket over a mess. Hopefully, documentation and tooling can be improved for a theoretically good but badly implemented solution. The other way around is not possible.
- dmitriid 5y ago
  > But the Nix way (how alien and complicated) is the theoretical sound way of handling dependencies. The approach may be sound, but the implementation and the user experience is atrocious, and can be quite easily[1] improved. [1] Easily as in: there have been multiple suggestions on what should be done to improve experience, but nix's codebase may not be conductive to that https://github.com/NixOS/nixpkgs/issues/93327#issuecomment-778546569 https://github.com/NixOS/nixpkgs/issues/93327#issuecomment-7... and nix contributors don't even see this as an issue https://github.com/NixOS/nixpkgs/issues/93327#issuecomment-661986395 https://github.com/NixOS/nixpkgs/issues/93327#issuecomment-6...

ducktective 5y ago

But the Nix way (how alien and complicated) is the theoretical sound way of handling dependencies. The docker solution is a blanket over a mess. Hopefully, documentation and tooling can be improved for a theoretically good but badly implemented solution. The other way around is not possible.

dmitriid 5y ago
> But the Nix way (how alien and complicated) is the theoretical sound way of handling dependencies. The approach may be sound, but the implementation and the user experience is atrocious, and can be quite easily[1] improved. [1] Easily as in: there have been multiple suggestions on what should be done to improve experience, but nix's codebase may not be conductive to that https://github.com/NixOS/nixpkgs/issues/93327#issuecomment-778546569 https://github.com/NixOS/nixpkgs/issues/93327#issuecomment-7... and nix contributors don't even see this as an issue https://github.com/NixOS/nixpkgs/issues/93327#issuecomment-661986395 https://github.com/NixOS/nixpkgs/issues/93327#issuecomment-6...