| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
|
|
|
|
| |
With hat: portmgr
Sponsored by: Absolight
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
| |
Approved by: gnome (kwm)
Security: 3b5c2362-bd07-11e5-b7ef-5453ed2e2b49
Security: CVE-2012-4504
|
|
|
|
|
| |
With hat: perl@
Sponsored by: Absolight
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before, we had:
site_perl : lib/perl5/site_perl/5.18
site_perl/perl_arch : lib/perl5/site_perl/5.18/mach
perl_man3 : lib/perl5/5.18/man/man3
Now we have:
site_perl : lib/perl5/site_perl
site_arch : lib/perl5/site_perl/mach/5.18
perl_man3 : lib/perl5/site_perl/man/man3
Modules without any .so will be installed at the same place regardless of the
Perl version, minimizing the upgrade when the major Perl version is changed.
It uses a version dependent directory for modules with compiled bits.
As PERL_ARCH is no longer needed in plists, it has been removed from
PLIST_SUB.
The USE_PERL5=fixpacklist keyword is removed, the .packlist file is now
always removed, as is perllocal.pod.
The old site_perl and site_perl/arch directories have been kept in the
default Perl @INC for all Perl ports, and will be phased out as these old
Perl versions expire.
PR: 194969
Differential Revision: https://reviews.freebsd.org/D1019
Exp-run by: antoine
Reviewed by: perl@
Approved by: portmgr
|
|
|
|
|
|
|
| |
noop fixes.)
With hat: perl@
Sponsored by: Absolight
|
| |
|
|
|
|
| |
net)
|
|
|
|
| |
Approved by: portmgr (bapt@, blanket)
|
|
|