Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"stack new --bare" will overwrite files #1597

mgsloan opened this issue Jan 3, 2016 · 2 comments

"stack new --bare" will overwrite files #1597

mgsloan opened this issue Jan 3, 2016 · 2 comments


Copy link

mgsloan commented Jan 3, 2016

It seems like somewhere along the line, the intention of 9b2c441 was lost (to have stack new --force indicate that overwriting files is ok). Maybe --bare without --force should require that the current directory is empty?

mgsloan referenced this issue in harendra-kumar/stack Jan 3, 2016
Currently stack init --solver cannot be used with a specific resolver.
It just uses the GHC on your path and provides a compiler resolver
corresponding to that GHC and all deps are extra deps.

Instead, we want to be able to use a specific snapshot and only deps not
matching the snapshot should be extra deps. This commit is a step towards
that goal.

1) '--solver' is now a switch which can be used along with a resolver.
    'stack init --resolver lts-2.22 --solver' will now be a valid init

2)  Snapshot selector now returns the snapshot with least number of
    dependency errors as a partial match. This snapshot is to be used
    by the solver.

    Note that the solver is not yet changed to work on an existing
    snapshot. That will come in a future commit.

3)  We now report an explicit error when the specified resolver does not
    have a compiler compatible with the package dependencies.

4)  Note a behavior change for the 'stack init --resolver' command. Earlier it
    used to write the stack.yaml file even if it did not successully resolve all
    packages. Now it will fail in that case and suggest '--solver' to
    resolve the extra dependencies.

5)  Separate the snapshot selection interface from the snapshot
    dependency check interface.

6) Some error message reporting changes.
Copy link

borsboom commented Jan 6, 2016


Copy link
Contributor Author

mgsloan commented Feb 18, 2016


@mgsloan mgsloan closed this as completed Feb 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants