commercialhaskell/stack

Allow --pvp-bounds to use multiple stack.yaml configurations

Open

#2,262 opened on Jun 9, 2016

View on GitHub
 (7 comments) (1 reaction) (1 assignee)Haskell (848 forks)batch import
component: releaseshelp wantedtype: enhancement

Repository metrics

Stars
 (4,060 stars)
PR merge metrics
 (Avg merge 17d 10h) (6 merged PRs in 30d)

Description

This is split off from https://github.com/commercialhaskell/stack/issues/1568, which focused on having multiple configurations in a single stack.yaml file.

As @sjakobi suggests, it's quite reasonable to still have a --pvp-bounds flag which uses multiple configs:

How about specifying the extra stack.yamls to consider with an optional flag to --pvp-bounds, e.g. --also-considering? Example command: stack sdist --pvp-bounds both --also-considering stack-7.8.yaml stack-8.0.yaml.

Folks would probably want to automate this via a Makefile or script.

Contributor guide

Research direction
Examine how the current pvp bounds flag is implemented in stack's codebase, and how stack reads and merges stack.yaml configurations. Then design a way to accept multiple YAML file paths via an optional flag like also considering and combine their pvp bounds settings.
Tech stack
haskell
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
HaskellGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70