Keeping direct dependencies distinct from external locks #3159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
May I ask for what purpose you use external_lock? Azure functions?
Viktor Svub <[email protected]> schrieb am Mi., 18. Apr. 2018, 09:57:
… just cosmetic and debuggability improvements, as we move to use the
external_lock feature 👍
- introduced new PackageRequirementSource to track external lock files
referenced from dependency files
- updated code relying on the union to behave correctly with the new
type -- currently equal to normal dependency file, except for logging
------------------------------
You can view, comment on, or merge this pull request online at:
#3159
Commit Summary
- Merge upstream master d818889 (5.143.0 release_notes) from
fsprojects/Paket:master
- Merge upstream/5.148.0 from fsprojects/Paket
- Merge upstream/5.151.1 from fsprojects/Paket
- Merge upstream/5.156.1 from fsprojects/Paket
- keeping direct depednencies distinct from external locks
File Changes
- *M* src/Paket.Core/Dependencies/PackageResolver.fs
<https://github.com/fsprojects/Paket/pull/3159/files#diff-0> (10)
- *M* src/Paket.Core/PaketConfigFiles/DependenciesFile.fs
<https://github.com/fsprojects/Paket/pull/3159/files#diff-1> (15)
- *M* src/Paket.Core/Versioning/Requirements.fs
<https://github.com/fsprojects/Paket/pull/3159/files#diff-2> (4)
Patch Links:
- https://github.com/fsprojects/Paket/pull/3159.patch
- https://github.com/fsprojects/Paket/pull/3159.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3159>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADgNC-Pf3PIxa20oetEQ5noRdvR7OJ_ks5tpvHVgaJpZM4TZl1A>
.
|
|
Not yet -- currently I plan to use this internally to enforce consistent external dependencies across our builds. We create lower hundreds of both interim and production components, and they use some external dependencies which we want to update in controlled way, and still keep them part of the resolve graph, to enforce compatibility with the unfixed ones. |
|
thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
just cosmetic and debuggability improvements, as we move to use the external_lock feature 👍