-
-
Notifications
You must be signed in to change notification settings - Fork 422
Added --install-in-builtin-dir
flag to lib install
command
#2077
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
Conversation
Codecov ReportBase: 36.64% // Head: 36.60% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@ ## master #2077 +/- ## ========================================== - Coverage 36.64% 36.60% -0.04% ========================================== Files 229 229 Lines 19471 19491 +20 ========================================== Hits 7135 7135 - Misses 11498 11518 +20 Partials 838 838
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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