Skip to content

Stop using lukko#338

Open
Bodigrim wants to merge 1 commit into
masterfrom
no-lukko
Open

Stop using lukko#338
Bodigrim wants to merge 1 commit into
masterfrom
no-lukko

Conversation

@Bodigrim
Copy link
Copy Markdown
Contributor

A year ago we stopped using lukko package by default and guarded it by a Cabal flag. No one complained and I never heard of anyone forcing the Cabal flag to use lukko instead of base. I think it's time we clean it up entirely.

Copy link
Copy Markdown
Member

@andreasabel andreasabel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. lukko does not seem to get upgraded to GHC 9.14, so it makes sense to drop it.

Comment thread cabal.haskell-ci
base-compat >= 0.12.2

constraint-set no-lukko
constraints: hackage-security -lukko
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was probably the wrong way round: since lukko was off by default, this constraint-set did not test anything (I suppose the intention was to actually test lukko). This explains why CI on GHC 9.14 did not fail despite lukko not being available.

@andreasabel
Copy link
Copy Markdown
Member

@Bodigrim Do you have rights to merge this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants