Skip to content

Remove Package.resolved and move to depending on HEAD #91

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

Merged
merged 4 commits into from
Mar 7, 2019

Conversation

benlangmuir
Copy link
Contributor

Always use the latest indexstore-db and swiftpm from the corresponding branch (currently master). This is important for swiftpm, because it does not guarantee stable behaviour, so we need to match the version. It also makes sourcekit-lsp behave more like the rest of the swift toolchain projects, who all live on HEAD for their dependencies.

Always use the latest indexstore-db and swiftpm from the corresponding
branch (currently master). This is important for swiftpm, because it
does not *guarantee* stable behaviour, so we need to match the version.
It also makes sourcekit-lsp behave more like the rest of the swift
toolchain projects, who all live on HEAD for their dependencies.
Now that we are building with HEAD swiftpm, change the recommended
toolchain to be whatever the latest available snapshot is. If you are
developing on ToT sourcekit-lsp, then using the latest snapshot is going
to have the closest match other than building the whole toolchain from
source.
Now that we build with HEAD, developers are more likely to need to run
swift-package-udpate themselves, so mention it in the build
instructions.
@benlangmuir
Copy link
Contributor Author

Please test with following pull request:
swiftlang/swift-package-manager#2031

@swift-ci please test

@benlangmuir benlangmuir requested a review from aciidgh March 7, 2019 18:11
@benlangmuir benlangmuir merged commit 4278f97 into swiftlang:master Mar 7, 2019
@benlangmuir benlangmuir deleted the head-deps branch March 7, 2019 23:44
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