Skip to content

Keeping direct dependencies distinct from external locks - #3159

Merged
forki merged 5 commits into
fsprojects:masterfrom
viktor-svub:feature/extern-lock-clean
Apr 18, 2018
Merged

forki merged 5 commits into
fsprojects:masterfrom
viktor-svub:feature/extern-lock-clean

Conversation

@viktor-svub

Copy link
Copy Markdown
Contributor

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

@forki

forki commented Apr 18, 2018 via email

Copy link
Copy Markdown
Member

@viktor-svub

Copy link
Copy Markdown
Contributor Author

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.

@forki
forki merged commit ac87a9f into fsprojects:master Apr 18, 2018
@forki

forki commented Apr 18, 2018

Copy link
Copy Markdown
Member

thanks!

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