[Webkit-unassigned] [Bug 115180] [GTK] Compile only WebKit2 by default

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Aug 8 06:38:40 PDT 2013


https://bugs.webkit.org/show_bug.cgi?id=115180





--- Comment #10 from Zan Dobersek <zandobersek at gmail.com>  2013-08-08 06:38:19 PST ---
I agree with the WK2 testing coverage on all points, it's basically just a matter of determining which underlying hardware should be tasked with testing what configuration, and executing that. Of course it's important to get this done quick enough as the focus is on WK2 now.

Also related, it should be discussed what amount of focus should be left on WebKit1 - API additions are already not welcomed there anymore, though basically most of the testing coverage is still on that variant.

Putting that aside and focusing on the scope of this patch, I'd recommend disabling WebKit1 builds by default only in the Autotools build system. Developers and Buildbot builders should still rely on build-webkit's --no-webkit1 and --no-webkit2 flags to get the desired configuration. Similarly, I don't think the additional --webkit1 flag is needed.

In short - release builds (straight via configure) should disable WK1 by default, developer builds (through build-webkit) should still enable WK1 unless specifically disabled (via --no-webkit1), at most until support for WK1GTK+ and all of its related code is thrown out of the source tree.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list