feat(installer): add Windows lba shim (v0.19.64) - #1
Closed
Ivanbeethoven wants to merge 2 commits into
Closed
Conversation
Signed-off-by: Luxian <lux1an@qq.com>
Signed-off-by: Luxian <lux1an@qq.com>
Owner
Author
|
Superseded by libra-tools#448. |
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
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.
Summary
libra-windows-amd64.exewith optional SHA-256 verificationlba.cmdshim, opt-out switches, and conservative uninstall handling0.19.64Impact
Windows users can install the release binary with
install.ps1and invoke Libra through the documentedlbashim without overwriting unmanaged binaries or aliases.Validation
powershell.exe ... tests/compat/install_alias_windows.ps1install.ps1andtests/compat/install_alias_windows.ps1cargo +nightly fmt --all -- --checkgit diff --checkcargo test --test compat_install_aliascould not run locally because the Windows environment lacks a complete Perl runtime andlibclang; the changed installer path is covered directly by the PowerShell smoke.