On Thu, Mar 05, 2026 at 08:44:25AM +0100, Henning Thielemann wrote:
Yes, that's one of the potential obstacles, but making automatic does not help. The solver does not see the conflict, even if `tsl` declares `conflicts: cryptonite`, and the flag is automatic.
What is `conflicts: cryptonite`? A Cabal package description field? I do not see it in Cabal-3.16 docs.
AI hallucination apparently. I was on a plane with spotty Wifi, and tried to make to with bad advice from Gemini. So it seems there isn't any practical way to express that `tls` **requires** the `use_crypton` flag in `mlkem` not only in its own build, but also when built as a dependency of other packages. :-( What is the correct way out of this bind? -- Viktor. 🇺🇦 Слава Україні!