Libproxy exists to answer the question: Given a network resource, how do I
reach it? It handles all the details, enabling you to get back to
programming.
This plug-in allows the KDE Desktop to make use of libproxy.
net/libproxy: update to 0.5.9
Completely rewritten since 0.5.0. Plugin ports are gone, they are
now built directly into the library.
PR: 284088
Reviewed by: arrowd
exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D48469
Fix WWW in parent/child ports
Many of the WWW are overwritten later which means the wrong value
is used. This did not happen before where the children were either
a) just using the pkg-descr from the parents
b) or had their own separate pkg-descr with custom WWW
Use WWW?= in parents when the child's WWW is different.
Children that use the same WWW as the parent can just inherit it,
i.e., the child WWW can be removed.
Approved by: portmgr (implicit)
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
net/libproxy: update to 0.4.17
- mark libproxy-mozjs borken
- add new port for pacrunner
- drop support for python2
Changelog:
- 0.4.16:
* Port to, and require, SpiderMonkey 68
* Use closesocket() instead of close() on Windows
* Add symbol versions - be ready to introduce new APIs as needed
* Add public px_proxy_factory_free_proxies function
* Add PacRunner config backend (largely untested; feedback welcome!)
* Small performance improvements
* pxgsettings: use the correct syntax to connect to the changed signal
(silences annoying output on console)
* Support python3 up to version 3.9
* Fix buffer overflow when PAC is enabled (CVE-2020-26154)
* Rewrite url::recvline to be nonrecursive (CVE-2020-25219)
* Remove nonfunctional and crashy pacrunner caching
* Never use system libmodman (no other consumers, not maintained)
- 0.4.17:
* python bindings: fix "TypeError: argtypes must be a sequence of types"
(#125)
Fix Qt5 symbol version scripts to put the catch-all clause first. When
a symbol matches multiple clauses the last one takes precedence. If the
catch-all is last it captures everything. In the case of Qt5 libraries
this caused all symbols to have a Qt_5 label while some should have
Qt_5_PRIVATE_API. This only affects lld because GNU ld always gives the
catch-all lowest priority.
Older versions of Qt5Webengine exported some memory allocation symbols from
the bundled Chromium. Version 5.9 stopped exporting these [1] but the
symbols were kept as weak wrappers for the standard allocation functions to
maintain binary compatibility. [2][3] The problem is that the call to the
standard function in these weak wrappers is only resolved to the standard
function if there's a call to this standard function in other parts of
Qt5Webengine, because only then is there a non-weak symbol that takes
precedence over the weak one. If there's no such non-weak symbol the call
(Only the first 15 lines of the commit message are shown above )
Mark QT4 ports/functionality for removal on 2019-03-15
While here, chase some KDE4 ports and functionality, these are scheduled for
removal on 2018-12-31. Change the default option/flavor to QT5 where applicable
or use alternative toolkits like GTK.
Submitted by: tcberner
Reviewed by: adridg, jhale, rene, tcberner
Approved by: portmgr (implicit, flavor hook)
Differential Revision: https://reviews.freebsd.org/D17741
Update net/libproxy to 0.4.15
* this release switched the build system to cmake
* move libproxy-gnome to libproxy-gnome2 for consistency
* add new slave libproxy-webkit3
* try to simplify the whole thing
* bump revisions in the dependencies
Reviewed by: gnome (kwm), mat
Differential Revision: https://reviews.freebsd.org/D15655
Rename KDE4 meta ports
This is done for
* consistency,
* and to simplify the import of the newer KDE Plasma5 desktop and KDE
applications
Bumps the dependencies.
Reviewed by: adridg
Differential Revision: https://reviews.freebsd.org/D12979
Replace Mk/bsd.kde4.mk by Mk/Uses/kde.mk in preparation for KDE Frameworks and
Plasma5 ports
At the moment KDE ports use bsd.kde4.mk to handle their dependencies. When
working on the ports for KDE Frameworks and Plasma5 it seemed to be more
reasonable to create a new kde.mk instead of adding an bsd.kde5.mk.
The kde.mk in this review is a stripped down version of the one we are using in
the KDE Test repositories plasma5 branch [1] to only contain the parts relevant
to the current KDE4 ports in the portstree [2].
Changes to the KDE Ports needed by this:
Replace USE_KDE4 by USE_KDE [3]
Add USES=kde:4 [4]
(Only the first 15 lines of the commit message are shown above )
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
(Only the first 15 lines of the commit message are shown above )
Update the default version of GCC in the Ports Collection from GCC 4.7.4
to GCC 4.8.3.
Part II, Bump PORTREVISIONs.
PR: 192025
Tested by: antoine (-exp runs)
Approved by: portmgr (implicit)
Upgrade OpenEXR and ilmbase to 2.2.0.
GCC 4.2 in FreeBSD 8.X/9.X base is now too old to compile OpenEXR, so
GCC-based systems will upgrade to the default ports compiler (GCC 4.7
currently.)
Add two patches to OpenEXR to permit building it in a live system with
the older OpenEXR version installed. Bug report filed to upstream Github
at https://github.com/openexr/openexr/issues/130
Couple OpenEXR more tightly to ilmbase and require its exact .so
version.
Add UPDATING note, and bump PORTREVISION of all dependent ports.
Proto-STAGE hugin-devel, and mark it IGNORE because hugin is newer.
Approved by: portmgr (implicit for bumping PORTREVISION on unstaged ports)
