Drop Evolution from RHEL 10 #999
Merged
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
* Evolution was appreciated by customers for its excellent Microsoft Exchange support, but Thunderbird's Exchange support was subpar, but they're now investing in resolving that * Microsoft recently announced that they will only allow Graph API for accessing email on Office365 and we don't support it in Evolution as of now (this will affect older RHEL releases as well) * We cannot justify to maintain 2 separate desktop email clients in RHEL * Evolution Data Server will stay as its the integral part of the GNOME * Evolution is and will be available on Flathub * Removing Evolution will allow us to remove WebKitGTK from RHEL 10 See Red Hat internal https://issues.redhat.com/browse/DESKTOP-797 for more information.
This is news to me. Any information on this front? |
yselkowitz
reviewed
Oct 18, 2023
Comment on lines
+11
to
+12
| - evolution-ews | ||
| - evolution-ews-langpacks |
There was a problem hiding this comment.
@tpopela please note that evolution-ews includes both e-d-s and evolution plugins, and its continued presence means that evolution itself is still being pulled into ELN. There does not seem to be a built-in way to build only the e-d-s components. Furthermore, given your explanation in this PR wrt Exchange support, shouldn't this too be retired, and only e-d-s itself remain?
|
We're aware of this and working on it.
Dne st 18. 10. 2023 23:34 uživatel Yaakov Selkowitz <
***@***.***> napsal:
… ***@***.**** commented on this pull request.
------------------------------
In configs/sst_desktop_applications-evolution-data-server.yaml
<#999 (comment)>
:
> + - evolution-ews
+ - evolution-ews-langpacks
@tpopela <https://github.com/tpopela> please note that evolution-ews
includes both e-d-s and evolution plugins, and its continued presence means
that evolution itself is still being pulled into ELN. There does not seem
to be a built-in way to build only the e-d-s components. Furthermore, given
your explanation in this PR wrt Exchange support, shouldn't this too be
retired, and only e-d-s itself remain?
—
Reply to this email directly, view it on GitHub
<#999 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOLBN5UG4XYNAHUKMYTAU3YABDM5AVCNFSM6AAAAAA5YURBZGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTMOBWGE4TANJXHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
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.
See Red Hat internal https://issues.redhat.com/browse/DESKTOP-797 for more information.