eosinstaller: Make eosinstaller share the same OSTree #190
Conversation
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
EOS 7 does not builds another OSTree branch for eosinstaller anymore.
Which means it should share the same OSTree with eos product. The
original major difference is eos-installer-meta-${platform} package. We
can make gnome-initial-setup know how to launch the eos-installer
application in some circumstances with the same OSTree.
Fixes: endlessm/eos-build-meta#138
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.
EOS 7 does not builds another OSTree branch for eosinstaller anymore. Which means it should share the same OSTree with eos product. The original major difference is eos-installer-meta-${platform} package. We can make gnome-initial-setup know how to launch the eos-installer application in some circumstances with the same OSTree.
Fixes: endlessm/eos-build-meta#138