Add ghc-exactprint as an extra_package

The package only supports 9.4 onwards so just trying adding it as a package for these builds.

The package only supports 9.4 onwards so just trying adding it as a package for these builds.

How about we just drop support for GHC 9.2? head.hackage is only ever meant to target the latest GHC release onwards, so we are well within our rights to only support 9.4+.

I think we will do at least one more 9.2 release so I think it's sensible to keep support for it on head.hackage until we decide to no longer do releases. Spawning 8 jobs does add quite a lot of CI pressure though.

mentioned in issue ghc#22752

FYI Am am working on GHC 9.6.1 at https://github.com/alanz/ghc-exactprint/tree/ghc-9.6, and generally track ghc head at https://github.com/alanz/ghc-exactprint/tree/ghc-head

The latter branch is a bit out of date at the moment, but since aligning the GHC version with ghc-exactprint it is a trivial process to sync them.

I stopped keeping them up to date when unix-compat failed to build, even with head.hackage.

mentioned in commit 5fcc831b

mentioned in merge request !275 (closed)

added 125 commits

• 77605668...cca143be - 124 commits from branch master
• 369d5ea0 - ci: Add ghc-exactprint to extra_packages

Compare with previous version

added 27 commits

• 369d5ea0...96d81f4d - 24 commits from branch master
• 5bb08062 - ci: Add ghc-exactprint to extra_packages
• 561e6bd3 - ci: Improve bash hygiene in config.sh
• 812d804c - ci: Add ghc-exactprint

Compare with previous version

FYI the ghc-9.8 branch builds on GH with GHC 9.8.1 alpha4

https://github.com/alanz/ghc-exactprint/actions/runs/6277428560/job/17049151505

My branch https://github.com/alanz/ghc-exactprint/tree/ghc-head is currently in sync with GHC master, as per ghc!13238 (closed).

How can that be used to make this work?

I don't believe we test GHC 9.2 anymore in head.hackage's CI, so I believe that is no longer an obstacle. Perhaps we can just add a modern version of ghc-exactprint and it will work? (I've paged out a lot of the discussion here, so I apologize if I've forgotten something important that makes this difficult.)

It might be worth opening a separate MR for this, since this one is dormant and rather old at this point.