|
|
|
|
|
by _piif
1274 days ago
|
|
In addition to what the other replies mentioned, it's also possible to fall back to other methods like flatpak or a container (which programs like distrobox make very easy to set up and integrate with the host) in case a package in nixpkgs is either non-existant, outdated or broken and you don't have the knowledge or the time to create / modify the derivation yourself. For instance, personally I have everything gaming related set up inside an Arch container so I can trivially follow upstream (or the master branch for Mesa) without any friction and it works wonderfully. |
|
That, or simply using pkgsrc.
It also provides versioning and decoupling from the system, but also has the benefits of working on any Unix and to be predictably updated. It's also far more KISS than any aforementioned solution.
The only real downside is the build time, as pkgsrc is more or less a managed federation of Makefiles. Installing software can take more time than would solutions based on binary packages, but it's totally worth it for the technical simplicity it brings to reproducible userlands.