-
Notifications
You must be signed in to change notification settings - Fork 40
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 for packages sharing the same dependencies #32
Fix for packages sharing the same dependencies #32
Conversation
… the first package in bullseye.yaml would have the dependencies listed as part of the package dependencies
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
@jacobshirley we require a signed CLA before proceeding |
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.
Can you move the new e2e test into examples/shared_dependencies?
Sure, that's done now |
Also buildifier is failing. |
Apologies for the delay on this. Thank you for your feedback. Hopefully that's looking ok now |
Thank you! |
Hi there, I was running into issues where, if multiple packages depend on the same packages, only the first one in the list will receive them. By removing the performance code in the resolver, it appears to be fixed. I've added a test, which verifies the nginx has a module that is required by both 'nginx-full' and 'nginx-core', when only 'nginx-core' goes into the image.
Please feel free to close this PR and do a better fix if there is one.