• https://github.com/libproxy/libproxy/archive/0.4.15/ (Download)

• no_webkit
• bootstrap

• (2017-05-12) Updated to version: libproxy-0.4.15
• (2017-01-11) Updated to version: libproxy-0.4.14
• (2016-08-27) Updated to version: libproxy-0.4.13
• (2016-01-19) Updated to version: libproxy-0.4.12
• (2013-04-14) Updated to version: libproxy-0.4.11
• (2012-11-27) Updated to version: libproxy-0.4.10
• (2012-10-12) Updated to version: libproxy-0.4.9
• (2012-03-29) Updated to version: libproxy-0.4.7
• (2011-03-24) Updated to version: libproxy-0.4.6
• (2009-04-04) Package added to openports.se, version libproxy-0.2.3 (created)

Log message:
replace simple PERMIT_PACKAGE_CDROM=Yes with PERMIT_PACKAGE=Yes

Log message:
Unbreak libproxy with upcoming ninja 1.9.0 update.
Rename cmake target "test" to avoid multiple ninja targets.
"sure" ajacoutot@ (maintainer), spotted by naddy@ Thanks

Log message:
bump all the py3 things, _SYSTEM_VERSION didn't quite work out how
we expected and it's easier|safer to do it this way than fiddle with
pkg_add now. thanks aja for update tests with a quick bulk.

Log message:
Recognize python 3.7 and 3.8, from upstream via ajacoutot in response to a
slightly different diff from me

Log message:
Add COMPILER lines to c++ ports which currently use the default. Adjust
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.

Log message:
bump LIBCXX/LIBECXX/COMPILER_LIBCXX ports.

Log message:
use COMPILER_LIBCXX where applicable

Log message:
Update to libproxy-0.4.15.

Log message:
Switch to a simpler clang fix from FreeBSD: just stop defining _POSIX_C_SOURCE
rather than raising the version, and that way _BSD_SOURCE isn't needed either.
Pointed out by ajacoutot.

Log message:
fix net/libproxy with libc++ by defining _POSIX_C_SOURCE=200809L and _BSD_SOURCE
clues from kettenis, espie

Log message:
use LIBCXX

Log message:
Add perl to WANTLIB, second batch. This used to be done automatically but
since SHARED_ONLY support was removed across the ports tree the perl module
no longer adds it, so it must be done manually for any perl ports that
provide perl shared-library modules (i.e. libdata/perl5/site_perl/$ARCH/*.so)
and you must not remove them from WANTLIB even if they show as "Extra".

Log message:
Update to libproxy-0.4.14.

Log message:
Update to libproxy-0.4.13.
- drop gettext module
- take maintainer

Log message:
Add a patch to prevent a null pointer dereference in net/libproxy under Gnome
Qt5 started to use libproxy and this exposed a crashing bug on OpenBSD
when using Qt5 applications on Gnome 3.
Here's a sample backtrace:
https://gist.github.com/mulander/c03997ae7e3fe4e30af0d4f2ce2965f0
The issue is caused by an unguarded dereference of ign_ip.
Other parts of the code properly expect that sockaddr_from_string
might return null and guard against it.
Adding a proper guard prevents a segfault both in OpenBSD
www/otter-browser and devel/zeal.
Issue reported upstream in:
https://github.com/libproxy/libproxy/issues/24
OK zhuk@ aja@

Log message:
remove SHARED_ONLY from some stragglers

Log message:
Fix libproxy's shared lib version, ok aja@
cmake.port.mk sets LIBfoo_VERSION for cmake to use as appropriate,
but this only works when the library name matches between SHARED_LIBS
and the cmake infrastructure - in this case there's a mismatch with
"proxy" vs "libproxy".
This used to be handled in this port by patching cmake files but
that's awkward to maintain so no surprise it accidentally got lost
in the last update; replace it by setting appropriate CONFIGURE_ENV
and MAKE_ENV in the port Makefile instead which is more maintainable.
Build problem with dependent ports reported by nigel@.

Log message:
Update to libproxy-0.4.12.
Add KDE support.

Log message:
sync WANTLIB

Log message:
No need for default CMAKE_BUILD_TYPE.

Log message:
bump after default python version switch

Log message:
Typo, we're talking about a subpackage here, not a FLAVOR;

Log message:
Add ${MODGETTEXT_RUN_DEPENDS}.

Log message:
Add the EPOCH to the webkit dependency.
spotted by landry@

Log message:
Merge -gnome into -main.
landry@ is ok with the idea
ok jasper@

Log message:
Fix after recent webkit update.

Log message:
xulrunner build depends is only needed for the mozilla flavor... obviously.

Log message:
Add mozilla to the PSEUDO_FLAVOR list and don't build it by default:
xulrunner does not build on all arches.
Prodded by landry@

Log message:
cmake likes to link with -lpthread instead of -pthread, so prevent that.
Fix dependencies of all subpackages.

Log message:
Major update to libproxy-0.4.6.
Several patches from the FreeBSD port.
Create -mozilla and -webkit subpackages. Do NOT build -webkit by default
because of a cyclic dependency:
libproxy,-webkit -> webkit -> libsoup -> libproxy
tested in a bulk by landry@
ok landry@

Log message:
new depends

Log message:
new WANTLIB

Log message:
bumps for python

Log message:
use REVISION, checked with before/after make show=PKGNAMES (plus some
extra-careful checking where there are complicated PSEUDO_FLAVORS).

Log message:
WANTLIB changes after xcb addition and bump.

Log message:
CONFIGURE_ENV += PYTHON="${MODPY_BIN}" is inherited from the python module

Log message:
- don't trust configure to pick up the python version to use ; this allows
libproxy to compile when several python versions are installed
- safe bump
breakage reported by Julien Cabillot

Log message:
Unbreak package names. (missing PKGNAME-main and PKGNAME-gnome)