Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • H head.hackage
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Glasgow Haskell Compiler
  • head.hackage
  • Issues
  • #46
Closed
Open
Created Feb 15, 2022 by Matthew Pickering@mpickeringDeveloper

Reacting to Cabal/Cabal-syntax split

I ping @RyanGlScott for advice about how to react to the Cabal/Cabal-syntax split.

At the moment patching packages is a bit awkward because

  1. We include allow-newer: Cabal in the cabal.project file
  2. For HEAD we therefore need to build Setup.hs depending on both Cabal-3.7 and Cabal-syntax-3.7
  3. For 9.2 we need to build just depending on Cabal-3.6

I'm unsure how to best express this in a Cabal file. Any advice @RyanGlScott ?

Assignee
Assign to
Time tracking