stack.yaml: update to lts-10.0 #91

2017-12-23T01:13:36+01:00

ghost commented

2017-12-23 01:13:36 +01:00

(Migrated from github.com)

There is no content yet.

ghost commented

2017-12-23 01:15:24 +01:00

(Migrated from github.com)

Ran into issues with cabal new-build, so I tried stack and, since stack's ghc bindists do not work here, I updated stack.yaml to lts-10.0 in order to use the host GHC (8.2.2).

Ran into issues with `cabal new-build`, so I tried stack and, since stack's ghc bindists do not work here, I updated `stack.yaml` to `lts-10.0` in order to use the host GHC (8.2.2).

ghost commented

2017-12-23 02:30:58 +01:00

(Migrated from github.com)

One of the CI jobs fails due to the now missing extra deps, which are not needed with lts-10.0. I'd say travis-ci.yml should be adjusted. Thoughts?

tfausak commented

2017-12-23 02:46:56 +01:00

(Migrated from github.com)

I think the typical way to do this is to have a separate stack-lts-8.0.yaml and use that in CI instead of setting the --resolver.

I think the typical way to do this is to have a separate `stack-lts-8.0.yaml` and use that in CI instead of setting the `--resolver`.

ghost commented

2017-12-23 03:05:36 +01:00

(Migrated from github.com)

@tfausak, pushed a commit to that effect. But, looking at the rest of the commented out travis-ci.yml, I'm not sure this is what we want, or that we'd like to carry multiple stack.yaml files at all.

lspitzner commented

2017-12-28 20:29:43 +01:00

(Migrated from github.com)

Renamed the ghc-8.0 stack yaml to stack-8.0.2.yaml; Merged into dev branch
(github does not see that this is merged, probably because of the rebase and because the commits are not in master yet? doesn't really matter.)

Using --resolver only makes sense if your package always was on stackage, but that is not really an option for brittany. I think multiple stack yamls are the correct approach.

thanks!

Renamed the ghc-8.0 stack yaml to `stack-8.0.2.yaml`; Merged into `dev` branch (github does not see that this is merged, probably because of the rebase and because the commits are not in `master` yet? doesn't really matter.) Using `--resolver` only makes sense if your package always was on stackage, but that is not really an option for brittany. I think multiple stack yamls are the correct approach. thanks!

Pull request closed

This pull request cannot be reopened because the branch was deleted.

Sign in to join this conversation.

No reviewers

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: hexagoxel/brittany#91