New app strategy for ARM64 in the context of the new OOBE #254
Conversation
This file contains 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
It is expected that UDI snap will be replaced by Subiquity only. Thus GUI will only be supported if Flutter is supported on Windows. Thus, for ARM64, only TUI will be possible. Although we could add some checks to the existing NoSplashStrategy, I'd rather keep them orthogonal as other differences may be detected later on.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
EduardGomezEscandell
requested changes
Jul 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It is expected that UDI snap will be replaced by Subiquity only.
Thus GUI will only be supported if Flutter is supported on Windows.
Thus, for ARM64, only TUI will be possible.
Although we could add some checks to the existing NoSplashStrategy,
I'd rather keep them orthogonal as other differences may be detected later on.
The next step is the x64 strategy, which is more complicated, thus I preferred to push on a separate PR.