Plugins: add a way to mark plugins as bundling all deps #14925
Closed
+50
−12
Conversation
This file contains hidden or 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
A plugin distributed as an .ez file might choose to include all dependencies into its "fat .ez" file. For such plugins, the ensure_dependencies/` validation does not make as much sense, so let's introduce a way to mark such plugins using their .app file metadata, and skip the dependency list validation for them. `
… dependency DAG Self-contained plugins' dependencies should not be validated against the DAG.
Collaborator
Author
|
Closing because this change and follow-up changes are still not enough without revisiting the "one dependency, one app, one code path directory" assumption the |
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.
A plugin distributed as an .ez file might choose to include all dependencies into its "fat .ez".
For such plugins, the
ensure_dependencies/1validation does not make as much sense, so let's introduce a way to mark such plugins using their .app file metadata, and skip the dependency list validation for them.