Ah, I think I understand what you’re saying.
You want a way to regenerate it, using the same state of Hackage, so that the only changes are the things you’ve added/removed in
However, you don’t want to use the directions from https://www.youtube.com/watch?v=qX0mgtSm360 to update it, because then you get a bunch of unrelated package updates from Hackage?
I’m not sure if there is a way to easily regenerate it based on the old state of Hackage.
I’d suggest looking through the
hackage2nix source code to see if you can find any command line arguments that may be relevant:
Or maybe the script from teto’s PR helps?
Another possibility is to split your PR into two:
- A PR that adds changes in
- A PR that adds fixes to
We could go ahead add merge in (1), wait a day for hackage-packages.nix to be updated, and then rebase (2) on top of it.
This is slightly more work, but then you don’t have to worry about regenerating hackage-packages.nix locally.