霜窗分径，文卷得渡 · Use PowerShell for Windows PDF install - #48
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The 0.5.4 dry-run proved that
pdfium-nativedownloads and verifies both Windows prebuilds, then fails because Git Bash GNU tar interprets the drive-letter colon as a remote host separator.This change runs the Windows Document install smoke under PowerShell/system tar, keeps Unix under Bash, and discloses the upstream Git Bash limitation in the Preview README.
Failure evidence: run 30235900658. Four Unix platform smokes already passed real PDF render + OCR.