commercialhaskell/stack

Special case for dependency mismatch on wired-in packages

Open

#2,696 创建于 2016年10月10日

在 GitHub 查看
 (0 评论) (1 反应) (0 负责人)Haskell (4,060 star) (848 fork)batch import
awaiting pull requestcomponent: output (UI/UX)help wanted

描述

In https://github.com/commercialhaskell/stack/issues/2553 , there is the following output:

In the dependencies for haddock-issue-0.1.0.0:
    base must match >=4.7 && <5, but the stack configuration has no specified version (latest applicable is 4.9.0.0)

Recommended action: try adding the following to your extra-deps in /home/simon/tmp/haddock-issue/stack.yaml:
- base-4.9.0.0

For wired-in packages, it would be good to suggest changing ghc version. For base versions, we could even consider hardcoding an association between base versions and ghc versions. This way, a different selection of compiler can be suggested as a possible "Recommended action"

贡献者指南

技术栈
无
领域
build system
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Familiarity with Stack dependency resolution
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate how Stack currently handles dependency mismatches for wired in packages like base. Look at the error output and the recommendation algorithm in the Stack codebase, likely in modules related to dependency solving or snapshot handling. Consider associating base versions with GHC versions to suggest a compiler upgrade instead of adding extra deps. The issue references #2553 for context; reviewing that issue and the linked code will help understand the current behavior.
Special case for dependency mismatch on wired-in packages · commercialhaskell/stack#2696 | Good First Issue