It's currently enabled by default by webkit-build, but disabled in configure. We should enable it in configure so that unstable releases will build webkit2 by default.
Created attachment 136841 [details] Patch
Comment on attachment 136841 [details] Patch Exciting! We need to take care of the library versioning before the next release though.
Committed r114084: <http://trac.webkit.org/changeset/114084>
Does this mean we want distributions to start shipping webkit2? I think it would be good to make sure we state it's still unstable API-wise, but I'll be happy to ship webkit2 packages in Debian =)
(In reply to comment #4) > Does this mean we want distributions to start shipping webkit2? I think it would be good to make sure we state it's still unstable API-wise, but I'll be happy to ship webkit2 packages in Debian =) That's a good point. Perhaps we should wait to do this until the last moment. The versions of WebKit2 before the next stable release are not API stable.
I think it's up to distros to decide, we have only enabled webkit2 option in configure by default in current trunk, not in the stable branch. That means that unstable releases will build webkit2 by default, but like any other unstable release cycle, the API might change.
(In reply to comment #6) > I think it's up to distros to decide, we have only enabled webkit2 option in configure by default in current trunk, not in the stable branch. That means that unstable releases will build webkit2 by default, but like any other unstable release cycle, the API might change. We'll have to be pretty clear about this in release notes and elsewhere, becuase up to this point, we rarely break API even in unstable branches.
(In reply to comment #7) > (In reply to comment #6) > > I think it's up to distros to decide, we have only enabled webkit2 option in configure by default in current trunk, not in the stable branch. That means that unstable releases will build webkit2 by default, but like any other unstable release cycle, the API might change. > > We'll have to be pretty clear about this in release notes and elsewhere, becuase up to this point, we rarely break API even in unstable branches. Ok, I thought it was clear that the backwards compatibility guarantee only affects stable releases.
It might just be me worrying too much. I guess it is hint enough that it's only in unstable releases.