14:16 mat 

Remove ${PORTSDIR}/ from dependencies, categories m, n, o, and p.

With hat:	portmgr
Sponsored by:	Absolight

 

10:00 rakuco 

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)

 

12:55 rakuco 

Add upstream patch to fix CVE-2012-4504.

Approved by:	gnome (kwm)
Security:	3b5c2362-bd07-11e5-b7ef-5453ed2e2b49
Security:	CVE-2012-4504

 

23:03 bapt 

Support stage

 

04:12 marino 

net/libproxy-gnome: USES+= pkgconfig

Approved by:	portmgr (bapt, implicit)

 

22:10 bapt 

Add NO_STAGE all over the place in preparation for the staging support (cat:
net)

 

05:26 dinoex 

- update png to 1.5.10

18:29 kwm 

Update to 0.4.6.

06:47 dinoex 

- update to 1.4.1
Reviewed by:    exp8 run on pointyhat
Supported by:   miwi

11:46 dinoex 

- update to jpeg-8

13:57 dinoex 

- bump all port that indirectly depends on libjpeg and have not yet been bumped
or updated
Requested by:   edwin

05:28 marcus 

Add libproxy-gnome, a plug-in which allows GNOME applications to make use
of libproxy.