-
NixOps 4. Beyond the Fediversity project: Nix co-maintainer, Hercules CI
- Joined on
2024-03-01
I have ideas, but none are all that applicable now. This looks like an ok optimum.
This branch is already included in the target branch. There is nothing to merge.
Are you ok forgejo? I guess I'll close this then. GitHub would mark it as merged for you. Ok.
overlays; what's wrong with them?
I just wasted hours on a project that defined sources
in an overlay for convenient access to the pins. Isn't a package, so should be fine? Nope. It affects…
overlays; what's wrong with them?
It's a mechanism for modifying the package set; not purely extending them. This makes them less modular than other mechanisms, because if any two overlays…
Oh wait no actually that pkgs
it referenced was inputs.nixpkgs.legacyPackages
anyway, but I got confused for a sec. Anyway, it's more flexible now, and if you import it into an aarch64-linux
…
I prefer to avoid overlays, and I think we should decide the package version for our users, because that's essential for being able to control quality.
?
I did make a mistake coding this…