Added --install-in-builtin-dir
flag to lib install
command
#2077
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.
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)What kind of change does this PR introduce?
Adds
--install-in-builtin-dir
flag tolib install
command.What is the current behavior?
What is the new behavior?
When the
--install-in-builtin-dir
flag is set, the libraries are installed in the directory specified by thedirectories.builtin.libraries
configuration setting:The libraries installed inside the builtin directory are not automatically upgraded via
lib upgrade
. They can be upgraded anyway, by forcing an install of an already installed library.Does this PR introduce a breaking change, and is titled accordingly?
No
Other information