Closed endgame closed 1 year ago
Why the flag? Context: I'd be happy to send a PR to do the change but would be interested to know why we'd want the flag?
That was an initial guess, before I saw which way things were going to go in the community. I haven't had time to think much about this; are people writing their packages to support both cryptonite
and crypton
, or has everyone just moved over to crypton
?
So far I've seen just moves to crypton and issues that just ask to move to crypton.
none of these have so far AFAIK used a flag. (there are some more PRs unmerged as of yet, also not doing flags).
If those projects beneath us in the depgraph don't use a flag then there's no point us doing so either. The PR should be pretty straightforward, then. Only subtlety is you might need to change the cabal.ede
template and (in a separate PR, targeting your main PR) run scripts/generate --commit
to rebuild the service bindings.
cryptonite
has been forked tocrypton
for ongoing maintenance. We should support it with a flag, defaulting tocrypton
and falling back tocryptonite
.