mirror of
https://git.freebsd.org/ports.git
synced 2025-06-07 05:40:30 -04:00
13d74ef592
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)
32 lines
1.3 KiB
Text
32 lines
1.3 KiB
Text
commit f30191930114cc334e02bb471f2c547198cad91c
|
|
Author: Raphael Kubo da Costa <rakuco@FreeBSD.org>
|
|
Date: Mon Jan 18 20:19:09 2016 +0100
|
|
|
|
config_kde: Decide whether to build the module based only on WITH_KDE.
|
|
|
|
kreadconfig/kreadconfig5 are runtime dependencies only. As such, there
|
|
should not be a build-time dependency on those in CMake at all. In other
|
|
words, building without those binaries works perfectly fine, and they
|
|
are only required when running libproxy.
|
|
|
|
commit 8ca0db36983e9154c808288fea4cbdfc9a7ea4c5
|
|
Author: Raphael Kubo da Costa <rakuco@FreeBSD.org>
|
|
Date: Mon Jan 18 16:59:28 2016 +0100
|
|
|
|
Make the KDE config module optional again.
|
|
|
|
This is a follow-up to bd9bf72 ("Add generic KDE config module"): make
|
|
it possible for distributions to not build the KDE config module at all,
|
|
even if it does not have any dependencies on Qt/KDE/KF5.
|
|
--- libproxy/cmake/modules/config_kde.cmk.orig 2016-01-12 16:41:07 UTC
|
|
+++ libproxy/cmake/modules/config_kde.cmk
|
|
@@ -1,6 +1,4 @@
|
|
-find_program(KDE4_CONF kreadconfig)
|
|
-find_program(KF5_CONF kreadconfig5)
|
|
+option(WITH_KDE "Build module to read proxy settings from KDE4/KF5" ON)
|
|
|
|
-if (KDE4_CONF OR KF5_CONF)
|
|
- set(KDE_FOUND 1)
|
|
-endif()
|
|
+# There are no additional detections; kreadconfig (from KDE4) and kreadconfig5
|
|
+# (from KF5) are only needed at runtime.
|