Depending on how much you want to take on, it might be time to start your own nixpkgs branch that you use for your systems. I have my branch cmpkgs that tracks nixos-unstable. Ideally, it would just mirror nixos-unstable, but there’s usually something nixpkgs-related that I’m hacking on, or some cross-compiler fix that I’m carrying, etc.
Hm, this would be nice to look at in the future, but it seems kinda overkill right now, because I don’t really want to work on any package stuff or fix cross-compiler issues, also I wouldn’t know how to manage that, I could apply my patches but when the merge request gets added and there are some conflicts or leftovers from old patches, I don’t really want to manage that myself
I guess nixos cache also wouldn’t work if I use my own branch? which sucks because I’ll have to wait hours until every browser I use is compiled
That means you’ve done the Nix part right - but the code that the patch expects to be applied to differs too much from what is fetched by the original expression.
Looking closer at the first link, this is a patch for NixPkgs and not for fcitx5-mozc. Sorry, I had overlooked that part on the first answer.
In that case you can just import https://github.com/musjj/nixpkgs/tree/fcitx-mozc-bazel like any other NixPkgs (e.g. additional flake input) and pick the relevant package like you would do when choosing packages from unstable while having your system on release.
I’m using the local flake input because I had to fix some sha missmatches and update a broken url in the pull request and it felt cubersome to commit and push every try at this.
I thought I could just do fcitx5-mozc = inputs.mypkgs.fcitx5-mozc but that didn’t work nor anything else I tried to directly use inputs.mypkgs, but well, it works perfectly now this way, even better than I anticipated, because I can actually just add every individual package in my overlay that I changed and remove it if it gets merged in, without any configuration overhead, or easily add my own packages if I want to use them in my config! Thanks so much!