Re-enable webkit plugin as a module (and build against webkit3)

Bug #934088 reported by Iain Lane
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libproxy (Ubuntu)
Undecided
Unassigned

Bug Description

The webkit pacrunner was disabled because it brought in a heavy dependency stack to the main libproxy shared lib. This can be avoided with a simple patch to build the pacrunner as a module in a separate package. It's very desirable to have a pacrunner, otherwise users who get their proxy information in this way are left out in the cold.

libproxy (0.4.7-0ubuntu4) precise; urgency=low

  * Re-enable webkit pacrunner and build it into its own module package
    (adding a patch to the upstream build system required to achieve this).
  * Build with webkit3.

 -- Iain Lane <email address hidden> Fri, 17 Feb 2012 10:10:45 +0000

Related branches

Revision history for this message
Iain Lane (laney) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libproxy - 0.4.7-0ubuntu4

---------------
libproxy (0.4.7-0ubuntu4) precise; urgency=low

  * Re-enable webkit pacrunner and build it into its own module package
    (adding a patch to the upstream build system required to achieve this).
    (LP: #934088)
  * Build with webkit3.
 -- Iain Lane <email address hidden> Fri, 17 Feb 2012 10:10:45 +0000

Changed in libproxy (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers