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

Remove suggestions for legacy packages syntax #4330

Merged
merged 1 commit into from
Oct 2, 2018

Conversation

fosskers
Copy link
Contributor

@fosskers fosskers commented Oct 1, 2018

stack version: master as of a299ac652fde49d3b4b6a199c1a206220826da68

Stack no longer parses the location syntax, but still suggests it to users in examples in a stack.yaml produced by stack new.

This PR moves the suggestions to an improved comment section for extra-deps.

- Stack no longer parses this syntax. The suggestion has been moved
  to an improved comment section for `extra-deps`.
@@ -274,15 +274,23 @@ renderStackYaml p ignoredPackages dupPackages =
, "packages:"
, "- some-directory"
, "- https://example.com/foo/bar/baz-0.0.2.tar.gz"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still legal, or should this be in extra-deps too?

, "- location:"
, " git: https://github.com/commercialhaskell/stack.git"
, " commit: e7b331f14bcffb8367cd58fbfc8b40ec7642100a"
, "- location: https://github.com/commercialhaskell/stack/commit/e7b331f14bcffb8367cd58fbfc8b40ec7642100a"
, " subdirs:"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the indentation here correct?

@fosskers
Copy link
Contributor Author

fosskers commented Oct 1, 2018

The CI failures seem to be a Travis timeout.

@mihaimaruseac mihaimaruseac merged commit cf9b94d into commercialhaskell:master Oct 2, 2018
@fosskers fosskers deleted the init-comments branch October 2, 2018 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants