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

port to webkit2gtk-4.0 [$20] #8

Closed
decathorpe opened this issue Apr 18, 2017 · 3 comments
Closed

port to webkit2gtk-4.0 [$20] #8

decathorpe opened this issue Apr 18, 2017 · 3 comments
Labels
Priority: High To be addressed after any critical issues Status: Confirmed Verified by someone other than the reporter

Comments

@decathorpe
Copy link
Contributor

decathorpe commented Apr 18, 2017

webkitgtk-3.0 has been considered deprecated and insecure for some time. It even has already been removed from the repositories that will become fedora 27 (for a reasoning, see 1). This prevents me from building pantheon-mail for fedora, and could be considered a security risk even on elementaryOS.

geary has already been ported to webkit2gtk-4.0 (see the upstream commit 2). Maybe some of the work done there can be reused for pantheon-mail.


Did you help close this issue? Go claim the $20 bounty on Bountysource.

@danirabbit danirabbit added Priority: High To be addressed after any critical issues Status: Confirmed Verified by someone other than the reporter labels May 29, 2017
@cassidyjames
Copy link
Contributor

@tintou tintou added the Rewrite label Jul 26, 2017
@bilelmoussaoui
Copy link

Is anyone working on this? Should I just port pantheon mail to webkit2gtk 4 or there's something else that should be added?

@danirabbit
Copy link
Member

@bil-elmoussaoui there's a rewrite branch that uses WebKit2Gtk4 and changes the backend to be EDS/LibCamel based instead. Personally, I think it would be better to spend development time there to get it up to feature parity so we can ship the new code base. But if you'd like to port the current code base to WebKit2Gtk4 that would be appreciated to :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High To be addressed after any critical issues Status: Confirmed Verified by someone other than the reporter
Projects
None yet
Development

No branches or pull requests

5 participants