-
Notifications
You must be signed in to change notification settings - Fork 990
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
[feature] Consider the re-package concept #13171
Milestone
Comments
Closed
1 task
1 task
1 task
3 tasks
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is your suggestion?
When a package, that is built using artifacts from other packages, can be built, but completely isolating the transitive dependencies. For consumers of that package, the transitive dependencies will not exist.
This might be a useful mechanism for releasing, both internally, but also externally (to other users) without unveiling the internal packages.
I can see at least some custom commands that could implement this via user-side (collect binaries + re-package), but it could be interesting what a
--build=missing
means for this kind of package, how the information from dependencies is gathered, how the package_id can be computed while isolating the dependencies.Have you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: