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 (4,060 stars) (848 forks)batch import
component: releaseshelp wantedtype: enhancement

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

Tech stack
None
Domain
clideveloper experiencebuild system
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with Stack's command line parsingknowledge of stack.yaml loading logicHaskell basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue proposes a ` also considering` flag for `stack sdist pvp bounds` to specify additional stack.yaml files. The implementation would involve modifying the command line argument parsing in the `stack sdist` command (likely in `src/Stack/Sdist.hs` or similar) and adjusting the logic that reads and merges PVP bounds configurations. The suggestion from commenter sjakobi (see issue #2262) provides a concrete API. There are no linked pull requests, so the issue is open for implementation. Study the existing ` pvp bounds` implementation and the `stack.yaml` loading mechanism to understand where to add the new flag.