search

commercialhaskell / stackage-infrastructure

Deployment configuration for Stackage and tools. Central place for Stackage admins.
MIT License
0 stars 0 forks source link

Pull curator from source and drop patch #1

Open chreekat opened 7 months ago

chreekat commented 7 months ago

/stackage-builder/curator_hackage-server-T1023.patch

juhp commented 1 month ago

Where/how is it used btw?

chreekat commented 1 month ago

I used the patch in flake.nix, where I define the precise version of curator that gets deployed on the server. I had pinned the curator repo to whatever revision master pointed to at the time I started working on it.

My patch was merged upstream, so we just need to update the pin and drop the patch.

chreekat commented 1 month ago

https://github.com/commercialhaskell/stackage-infrastructure/blob/main/flake.nix#L319-L331

juhp commented 1 month ago

Okay, I guess my question is what do you actually use/need curator for?

We pull the curator binary directly for building snapshots. So maybe you just used it for testing etc?

chreekat commented 1 month ago

That's a great question. But it turns out there's a good answer. (I had to just double check :D )

The reason is that the curator repo is the source of both curator and casa-curator. The latter is actually what got patched. It runs as a background process on the server, keeping casa up to date.