Give a working evalPackages to package-set
I only use things like plan-to-nix and I don't use the project functions. Recently the introduction of evalPackages has broken my workflow.
Trying to include tools via withHoogle = true; or tools.cabal = "3.4.0.0"; would result in evalPackages being evaluated but being undefined.
Because the evalPackages defined in plan.nix was just a stub. I tried to expand it there but then it also needed evalSystem. Since project-common.nix already has working definitions for these and doesn't bring in too much else, I decided to just use that for package-sets. Not great but seems work well.
Sounds like a good workaround! I don't know who are the other users of plan-to-nix that could be affected by such changes?
I'm a bit uneasy that this pulls in lots of other stuff from project-common.nix. Would it make sense to have a project-and-package-set.nix with just the stuff we need (evalPackages and evalSystem)?