[codex] Use package-friendly runtime paths#103
Closed
besendorf wants to merge 1 commit into
Closed
Conversation
Collaborator
Author
|
Replaced by #104 with neutral branch and title naming. |
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.
Summary
androidqfexecutable.key.txtin the current working directory first, then fall back to the executable directory.Why
This is better for androidqf usage when it is installed via a package manager: packaged executables usually live in read-only or shared system locations, while runtime artifacts should be written to the user's working directory or a temporary directory.
Validation
go test ./...go test -tags unbundle ./...GOOS=darwin GOARCH=amd64 go test ./adb ./assetsGOOS=windows GOARCH=amd64 go test -tags unbundle ./adb ./assets