-
Notifications
You must be signed in to change notification settings - Fork 843
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
Fix failure to find package when a dependency is shared between projects (#5680) #5682
Conversation
@snoyberg Now, in addition to the file |
Built and tested locally (with Great work @borsboom and @drone-rites! |
This is great news, thanks for fixing! I'll also switch to this branch for local use until this fix makes it's way to a release. |
@borsboom I think single JSON makes sense |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work and nice integration test! Sorry for breaking this.
And yes, I think putting everything into a single JSON is cleaner, but it wouldn't be a blocker.
My recommendation would be cutting a release once this is merged and has at least a bit of testing.
@borsboom is planning on a release later this week. I believe it will be 2.7.5. |
This fixes a regression that was introduced in f641880 (the fix for #5578). Now, a package will be reconfigured if the project it's being built from (and therefore the local package database it gets installed to) changes.
The documentation has been updated, if necessary.(N/A)How I tested:
test/integration/tests/5680-share-package-across-projects