[wishlist] Build in WebKit support

Thank your for your bug. Webkit is not packaged yet and the backend is something under work and not stable enough to be distributed

Webkit is packaged now, and I having a seperate epiphany-webkit package would make sense.

Where are these packages located at? Upstream at Debian?

I most definitely do not see any WebKit package listed in Gutsy's repositories at the moment.

On Mon, 2007-09-10 at 16:33 +0000, Will Farrington wrote:
> Where are these packages located at? Upstream at Debian?
>
> I most definitely do not see any WebKit package listed in Gutsy's
> repositories at the moment.
>
http://packages.ubuntu.com/gutsy/source/webkit
--
Bruce Cowan <email address hidden>

Cool. Then yeah, epiphany-webkit definitely deserves its own package.

no, webkit is to universe and would need to be supported to build epiphany with it which we don't intend to do this cycle, the epiphany code is still not really stable anyway and there is no real interest for users

Of course the firefox-granparadiso package is totally different as it is Firefox.

What is being suggested is a new package called epiphany-webkit or something like that which is in universe.

the epiphany-browser source is to main, do you suggest duplicating the source package to have a webkit variant to universe? The distro team is not going to work on that, if you are wanting to taking responsability to update the duplicate source and deal with the bug let we know though

Fair enough.

I'll see what I can do with the situation.

I think that in a near future Epiphany with webkit support should be the default ubuntu browser and webkit should be default in gnome/gtk

i think we should use epiphany with webkit as defaultbrowser, too :D

Incidentally, Debian's Epiphany package has a WebKit version available : http://packages.debian.org/changelogs/pool/main/e/epiphany-browser/current/changelog

I've made a package based on Debian's version, it will be in my PPA if I'm ever accepted into the beta testers team.

This version is rather buggy and I would not encourage users to run it yet

Indeed, it is only for testing purposes. The back and forward buttons don't work, extensions and plugins don't work (I'll look into extensions), and scrolling is a bit odd.

https://launchpad.net/~bruce89/+archive

I'm trying to package 2.20.2, which requires me to run autoreconf to update 99_autoreconf.patch, which ends in "embed/Makefile.am: required file `./compile' not found".

Any advice would be much appreciated.

epiphany-browser (2.20.2-1ubuntu1) hardy; urgency=low

  * The webkit variant is not built for now since it's not juged good enough
    to compete with the gecko one yet and not worth promoting webkit.
    The package could be maintained to universe as a different source for now.

So, is the issue epiphany-browser's source package being in main, meaning that it can't build-depend on things outside of main? If that's the case, this seems to be a deficiency in the build system.

For instance, the xscreensaver source package produces 5 binaries, some of which are in universe. However, all the build dependencies of it are in main.

The patch 98_xulrunner1.9.patch breaks the WebKit build at "configure: error: conditional "HAVE_GECKO_XPCOM_GLUE" was never defined."

Requiring that the build depends of main software are in main is a choice and not a bug, it should be possible to build supported package using only supported components

Is the webkit backend stabler in 2.22? If so, perhaps the decision not to package it should be reconsidered.

It's not a question of stablility, WebKit would have to be in main for Epiphany to be able to built with it. WebKit is not a candidate for main yet, and probably won't be until KDE start requiring it for KDE 4.1.

On Wed, Mar 26, 2008 at 09:23:56PM -0000, Bruce Cowan wrote:
> It's not a question of stablility, WebKit would have to be in main for
> Epiphany to be able to built with it. WebKit is not a candidate for main
> yet, and probably won't be until KDE start requiring it for KDE 4.1.

Ah, sorry. Thanks for the explanation.

When you can't/won't build it officially, can you make a epiphany-webkit ppa build for hardy please?!

https://launchpad.net/~bruce89/+archive has only epiphany-gecko!

epiphany-webkit is not really usuable yet, why do you want a build? if you want to debug it you should better try to build directly the svn version

I tried to build a package, but it didn't work. I instead just compile both WebKit and Epiphany from SVN.

> epiphany-webkit is not really usuable yet, why do you want a build? if you want to debug it you should better try to build directly the svn version

When i can't evaluate it, i can't say it. Epiphany is released as Experimental Backend... no word about usability. Some posts above there was written that's a politic (cause not in main) decision and not a stability/technical/build problem?!

And i use Ubuntu, because i won't compile everything myself. This is why i switched from Gentoo to Ubuntu! ;) I do this often enough with other apps/libs, so i need no additional builds of standard applications for myself. And i've installed hardy, cause i want/need to use some experimental/more actual apps/libs.

Webkit will be the official backend in Epiphany for GNOME 2.24: http://mail.gnome.org/archives/epiphany-list/2008-April/msg00000.html

This bug was fixed in the package epiphany-browser - 2.22.3-1ubuntu1

---------------
epiphany-browser (2.22.3-1ubuntu1) intrepid; urgency=low

  * Sync on Debian
  * the webkit backend is built now (lp: #131944)
  * debian/control.in:
    - updated maintainer information
    - updated to the ubuntu xulrunner naming
  * debian/epiphany-browser-data.gconf-defaults:
    - change startup page
  * debian/patches/03_dbus.patch:
    - don't use hack from Debian to start a private instance when it can't
      connect to the dbus, changes made while running that mode are not stored
      (Ubuntu: #74725)
  * debian/patches/06_lpi.patch:
    - launchpad integration
  * debian/patches/08_localized_startup_page.patch:
    - use the startup page corresponding to the locale used
  * debian/patches/11_useragent-weasel.patch:
    - don't use, the change is Debian specific
  * debian/patches/80_from_upstream_fix_printing_scale.patch:
    - change from Paul Drain commited upstream to fix the default printing scale
  * debian/rules:
    - use dh_icons so the icon is correctly available after installation

 -- Sebastien Bacher <email address hidden> Mon, 14 Jul 2008 16:39:33 +0100

I can only assume that WebKit will be moving to main, otherwise, Ephy won't build now.

the build logs are public and webkit has been promoted several hours before you added your comment

Indeed, When I looked, there were failed to build logs. I'll be quiet now.

Could this be ported to hardy-backports please?