1
0
mirror of https://git.FreeBSD.org/ports.git synced 2024-12-16 03:24:07 +00:00
freebsd-ports/net/libproxy-kde/pkg-plist
Raphael Kubo da Costa 13d74ef592 Update libproxy and its slave ports to 0.4.12.
After being dormant since 2013, libproxy development picked up some steam at
the end of last year, and the project moved from Google Code to GitHub,
where its releases are also being hosted. A summary of changes between 0.4.6
and 0.4.12 can be found here:
    https://github.com/libproxy/libproxy/blob/0.4.12/NEWS

The libproxy ports themselves have undergone several changes too:
* net/libproxy
  - Drop a lot of patches that are no longer necessary.
  - Add a few patches that I have sent upstream, and add some context to the
    0.4.6 patches that are still required.
  - Explicitly disable a few build options (.NET bindings, for example).
  - Switch to an out-of-source CMake build (also applies to the slave
    ports).
  - Drop the unnecessary post-install target, likely added before pkg and
    our ports system got smart enough to remove directories when needed.
* net/libproxy-gnome
  - Explicitly add dependency on devel/glib20 as the code links against
    GObject.
  - Make it clear that this plug-in targets GNOME2 desktops and uses GConf
    to read proxy settings.
* net/libproxy-gnome3
  - New port. Similar to libproxy-gnome, but targets GNOME3/Mate and reads
    proxy settings via GSettings instead. libproxy-gnome retained its name
    to avoid confusing users and requiring instructions in UPDATING.
* net/libproxy-kde
  - The KDE configuration plug-in has been rewritten upstream and no longer
    links against Qt or any KDE libraries. Instead, it just has a run-time
    dependency on either kreadconfig (from KDE4) or kreadconfig5 (from KDE
    Frameworks 5).
* net/libproxy-mozjs
  - Resurrect the port; the plug-in has been rewritten and now uses
    lang/spidermonkey185 to parse the JavaScript in .pac files.
* net/libproxy-webkit
  - Switch to depending www/webkit-gtk3 instead of www/webkit-gtk2. In
    practice, there is no huge difference since libproxy only uses the
    JavaScriptCore layer (which is toolkit-independent) to parse .pac files.

Finally, thanks to mat@ for answering some questions about libproxy-perl and
which Perl patches still needed to be retained or rewritten.

Approved by:	gnome (kwm)
2016-01-19 10:00:25 +00:00

2 lines
47 B
Plaintext

lib/libproxy/%%VERSION%%/modules/config_kde.so