Remove chromium-wayland recipe and related tasks/settings. #63
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
This is a first step towards updating the main Chromium recipe to a more recent milestone. The ozone-wayland project has been unmaintained for a long time, and we will not be able to keep supporting it as-is without significant overhead; meanwhile, there has been work upstream to make Chromium work on Wayland, and we should be able to leverage it within a few milestones. Signed-off-by: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
otavio
approved these changes
Nov 13, 2017
|
@twoerner I am fine with this change. If you are fine too, please merge. |
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.
This is a first step towards updating the main Chromium recipe to a more
recent milestone. The ozone-wayland project has been unmaintained for a long
time, and we will not be able to keep supporting it as-is without
significant overhead; meanwhile, there has been work upstream to make
Chromium work on Wayland, and we should be able to leverage it within a few
milestones.
See also: #62.
Signed-off-by: Raphael Kubo da Costa raphael.kubo.da.costa@intel.com