Why does `stackage-curator` have its own `build-constraints.yaml`?

[massysett]

Currently its build-constraints.yaml is about ten days older than the one in the stackage repo. I am wondering if this caused one of my builds to fail:

commercialhaskell/stackage#1400 (comment)

The file

https://github.com/fpco/stackage/blob/master/DATA-FLOW.md

says stackage-curator "grabs the latest version" of build-constraints.yaml so I'm not sure where it is coming from.

[snoyberg]

It's just present for testing purposes, it doesn't have any effect. It's worth having a comment at the top explaining that that's its purpose. Feel like claiming the glory with a PR? ;)

[massysett]

Thanks, see

#16