summoner-tui constraints about summoner

[recursion-ninja]

@mouse07410 the following all compiled successfully for me:

summoner-cli

✓ GHC 9.0.2

cabal update
cabal install summoner --with-compiler=ghc-9.0.2 --allow-newer=base,ghc-prim

summoner-tui

✓ GHC 8.10.7

cabal update
cabal install summoner-tui --with-compiler=ghc-8.10.7 --allow-newer=base

✓ GHC 9.0.2

cabal update
cabal install summoner-tui --with-compiler=ghc-9.0.2 --allow-newer=base,ghc-prim

This suggests that relaxing dependency upper bounds is all that is currently required in order for summoner-cli to support ghc-9.0.2 and summoner-tui to support ghc-8.10.7 and ghc-9.0.2.

Additionally, I would like to note that relude does not compile with base-4.16.* because it re-exports the deprecated Option type. I suspect that as soon as relude is updated to support base-4.16.*, then both summoner-cli and summoner-tuiwill also compile with ghc-9.2.2.

Perhaps a PR bumping bounds is in order!?

[mouse07410]

the following all compiled successfully for me: . . .

I confirm that both summoner and summoner-tui compiled/installed fine with the flags you mentioned above.
Cabal-3.6.2.0, GHC-9.0.2.

Thanks!

[mouse07410]

summoner can't be built by GHC newer than 8.10.7, and summoner-tui - by GHC newer than 8.8.4.

It would be great if one could build both under, e.g., GHC-9.0.2. Or at least, GHC-8.10.7. Thanks!

[vrom911]

This should be solved in the main branch now 🙂

[mouse07410]

@vrom911 thank you for adding support for GHC 9.0.2 and 9.2.4.

However, please note that the current latest stable released GHC is 9.4.2. It would be nice to see it supported too.

[recursion-ninja]

Yes, support for the current GHC-9.4.* series, as well as planning for prompt support of the impending GHC-9.6.* series would be greatly appreciated!