-
Notifications
You must be signed in to change notification settings - Fork 694
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
Fix the root directory when building for Linux on Windows. #1609
Conversation
Otherwise, the .tar file gets a weird structure that is not well interpreted in Linux; e.g. files get names like ".\a\b\c\file" (that is a filename, not a path).
Please let me know if there is a better way to know if the Bazel host is Windows; I could not find a consistent approach elsewhere in rules_docker. |
/assign @alex1545 |
/gcbrun |
Oops, I may have clicked the wrong button. I was seeing a message saying this branch was out of date with the master. What is the next step for this Pull Request? |
/gcbrun |
/gcbrun |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: faube, smukherj1 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…d#1609) Otherwise, the .tar file gets a weird structure that is not well interpreted in Linux; e.g. files get names like ".\a\b\c\file" (that is a filename, not a path). Co-authored-by: Suvanjan Mukherjee <[email protected]>
…d#1609) Otherwise, the .tar file gets a weird structure that is not well interpreted in Linux; e.g. files get names like ".\a\b\c\file" (that is a filename, not a path). Co-authored-by: Suvanjan Mukherjee <[email protected]>
Otherwise, the .tar file gets a weird structure that is not well interpreted in Linux; e.g. files get names like ".\a\b\c\file" (that is a filename, not a path).