Randomly switch between buildInputs, nativeBuildInputs, depsBuildBuild, depsBuildTarget, depsHostHost, and depsTargetTarget until it builds.
Good luck building anything electron. Copy-paste some existing build recipe and replace the source. If it doesn’t work, make a post on the forums saying it doesn’t work and let somebody else figure it out, then create a PR 🫰 ezpz
I mean, fair enough; also, your use case is entirely unlike that of someone who just uses NixOS normally, I would imagine. It’s really not like using NixOS requires a deep understanding of the language itself, or at least that’s never been my experience with it, and I’ve been daily driving it for well over a year at this point. As long as I know enough to keep maintaining the same /etc/nixos/configuration.nix I have now indefinitely, that’s as deep of an “understanding” of the language as I will ever need, personally. I’m well aware that there are a lot of things I could be doing if I knew how to, and frankly, I’ll probably never learn how to do those things because I’ll probably never have to. NixOS is by far the single easiest distro I’ve ever used, if only because everything’s always reproducible and because nothing ever breaks.
No, it’s just I need niche proxy software so I maintain one package. The other package is bugged (wrong paths on nix), so I maintain a fork and a NUR package
Joke’s on you, I don’t understand Nix and I’m a NixOS package maintainer
I’m guessing you’re responsible for the documentation, as well.
Gottem lol
Kind of, but since I don’t know what I’m doing I mostly just delete some of it when it’s not working
teach us the way
is it possible to learn this power?
Randomly switch between
buildInputs,nativeBuildInputs,depsBuildBuild,depsBuildTarget,depsHostHost, anddepsTargetTargetuntil it builds.Good luck building anything electron. Copy-paste some existing build recipe and replace the source. If it doesn’t work, make a post on the forums saying it doesn’t work and let somebody else figure it out, then create a PR 🫰 ezpz
Anti Commercial-AI license
I don’t randomly switch between anything, I go straight to copy pasting existing packages
This is da wey!
Anti Commercial-AI license
Lol…
I mean, fair enough; also, your use case is entirely unlike that of someone who just uses NixOS normally, I would imagine. It’s really not like using NixOS requires a deep understanding of the language itself, or at least that’s never been my experience with it, and I’ve been daily driving it for well over a year at this point. As long as I know enough to keep maintaining the same
/etc/nixos/configuration.nixI have now indefinitely, that’s as deep of an “understanding” of the language as I will ever need, personally. I’m well aware that there are a lot of things I could be doing if I knew how to, and frankly, I’ll probably never learn how to do those things because I’ll probably never have to. NixOS is by far the single easiest distro I’ve ever used, if only because everything’s always reproducible and because nothing ever breaks.No, it’s just I need niche proxy software so I maintain one package. The other package is bugged (wrong paths on nix), so I maintain a fork and a NUR package
It’s not by choice!