Skip to content
Snippets Groups Projects

Document use of --allow-newer

Merged Brandon Chinn requested to merge brandonchinn178/head.hackage:template-haskell into master

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • I'm not sure how to feel about this. These patches certainly don't harm anything, but if we really wanted to be thorough, we'd have to raise the upper version bounds for a lot more than just template-haskell—we'd also need to cover base, ghc-prim, Cabal, etc. That is, anything that is mentioned in this list.

    head.hackage's CI takes the approach of always passing --allow-newer with these packages to avoid the busywork of needing to bump their upper version bounds for all packages (and dependencies). I wonder if it would be better to document that head.hackage users should be expected to do the same. What do you think?

  • Brandon Chinn added 1 commit

    added 1 commit

    • cca143be - Document use of --allow-newer

    Compare with previous version

  • Brandon Chinn changed title from Bump template-haskell bounds to Document use of --allow-newer

    changed title from Bump template-haskell bounds to Document use of --allow-newer

  • Brandon Chinn changed the description

    changed the description

  • Makes sense. Updated

  • Ryan Scott approved this merge request

    approved this merge request

  • I like it. Thanks!

  • merged

Please register or sign in to reply
Loading