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 Mozilla-based browsers to make use of libproxy.
WWW: http://code.google.com/p/libproxy/

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

- Remove www/libxul19, is has been vulnerable and unsupported upstream for
quite some time.
- Switch all remaining consumers to depend on www/libxul
- Mark ports that don't work with the new libxul BROKEN
- Mark some old ports DEPRECATED with a reasonable timeout
Approved by: portmgr (miwi)

Presenting GNOME 2.28.1 for FreeBSD. The official release notes for this
release can be found at http://library.gnome.org/misc/release-notes/2.28/ .
Officially, this is mostly a polishing release in preparation for GNOME 3.0
due in about a year.
On the FreeBSD front, though, a lot went into this release. Major thanks
goes to kwm and avl who did a lot of the porting work for this release.
In particular, kwm brought in Evolution MAPI support for better Microsoft
Exchange integration. Avl made sure that the new gobject introspection
repository ports were nicely compartmentalized so that large dependencies
aren't brought in wholesale.
But, every GNOME team member (ahze, avl, bland, kwm, mezz, and myself)
contributed to this release.