-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Rename file in single portable installs #3439
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
After discussing with the team, we want this change to be included in the next release as a hotfix for the single portable symlink bug. The portable install for the archive scenario is quite complicated and will need to be addressed in our 1.7 release. If you can resolve the merge conflicts and get the build passing, we'll go ahead and check this one in. Thanks for your help! |
Sounds good. I'll get it rebased later tonight and see what happens! |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
@ryfu-msft - I'm hoping that x64 failure has nothing to do with me and everything to do with a glitch in the fabric of reality? |
definitely the latter 😆, will kick it off again... |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
This should work for renaming whenever the portable is a loose binary, or when it is not inside of a directory in a zip file. With the way directory extraction works with Zip files, I wasn't able to add just a file entry to move the file since the Desired State entries are not guaranteed to process in order. I'd like some guidance on how that should be handled, perhaps that should be a separate PR?
Microsoft Reviewers: codeflow:open?pullrequest=#3439