Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by mikepurvis on Tuesday April 05, 2022 @01:06PM
(#30921671)
Flakes are actually part of the piece for how to sanely get access to old versions of things, as your project flake can bring in multiple instances of nixpkgs from different “stable” branches and then pull the specific packages off each one that you need.
[ Parent
| on HN ]
Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by qudat on Tuesday April 05, 2022 @08:35PM
(#30926968)
Just in this thread I have one person saying that I should avoid flakes and you are telling me it will save me. I think we proved my point.
Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by mikepurvis on Wednesday April 06, 2022 @08:24AM
(#30931240)
Fair, fair. A slightly more charitable take might be that flakes solve/streamline a set of problems that are particularly acute for power users, and installing multiple specific versions of software without needing to copy the definitions into your overlay is absolutely a power user move.
Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by soraminazuki on Wednesday April 06, 2022 @12:24AM
(#30928466)
Flakes are undeniably useful but it's gated behind an experimental flag and documentation work is ongoing. For now, it just shouldn't be the first point of entry for beginners.
Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by mikepurvis on Wednesday April 06, 2022 @08:26AM
(#30931258)
The documentation is the biggest gap for sure. I've only been using Nix for about a year, and I'm using flakes exclusively. Although I don't have direct experience with the legacy system, I could definitely picture it being very frustrating managing inputs via the NIXPATH envvar rather than explicitly with flake locking.