Skip to content
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

Merged
merged 2 commits into from Aug 30, 2023

Conversation

Trenly
Copy link
Contributor

@Trenly Trenly commented Jul 14, 2023

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=https://github.com/microsoft/winget-cli/pull/3439&drop=dogfoodAlpha

@Trenly Trenly requested a review from a team as a code owner July 14, 2023 18:06
@yao-msft
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@yao-msft
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ryfu-msft
Copy link
Contributor

@Trenly,

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!

@Trenly
Copy link
Contributor Author

Trenly commented Aug 29, 2023

@Trenly,

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!

@ryfu-msft
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

1 similar comment
@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Trenly
Copy link
Contributor Author

Trenly commented Aug 29, 2023

@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?

@ryfu-msft
Copy link
Contributor

@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...

@yao-msft
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@yao-msft yao-msft merged commit 6abb614 into microsoft:master Aug 30, 2023
8 checks passed
@Trenly Trenly deleted the renamePortable branch August 30, 2023 01:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants