- java implementation of an ssh client that hasn't been updated in 12 years;
- non-free and we can't update because the distfile is behind a registrationf
form now;
- oh, and it doesn't even work...
ok sthen@
squid 3.3.5. It also fixes ipv6 and other stuff, details of which can
be found here: https://code.google.com/p/sqtop/source/list
Update MAINTAINER email address at his request while here.
ok gonzalo (MAINTAINER) and sthen
have "not yet linked to the build" etc. in the commit log.
devel/hs-simple-sendfile
devel/jenkins
security/p5-Mozilla-CA
sysutils/uptimed
textproc/p5-Encode-Locale
www/p5-IO-HTML
www/webgui
- see http://www.mozilla.org/en-US/firefox/22.0/releasenotes/ (ok,
webrtc isnt enabled yet by default on *BSD but we're working on it :)
- fixes MFSA 2013-49->62
- remove all patches related to sydneyaudio which got removed upstream,
sound uses libcubeb which has a native sndio backend since ages (thx
to ratchov!). also remove related post-patch target while here.
- add temporary workaround (TERM=xterm) for bug #878089
- switch i386 to use clang again, using --disable-debug-symbols to make
the code smaller (who said 'gross hack' ?)
- update patch-gfx_thebes_gfxPlatform_cpp to match what got commited
upstream in r52b02042b27f
- remove patch-js_src_vm_SPSProfiler_cpp which unbroke powerpc, finally
got commited in 22 branch
- rework fx-i18n's MESSAGE to be more in line with reality (discussed
with Marcus Merighi)
rather than "transparent proxy"; switch the readme to match. also tweak the
wording to make it clear which firewall reals need to be on which machine
when having a router pass off http traffic to squid on a different machine
configured as an interception proxy.
a new libmysqlclient non-blocking API which utilizes co-routines. The X86
specific GCC ASM co-routine support hid the fact that there was an issue.
The only fallback code so far is POSIX user contexts which OpenBSD does not
support.
Input from and Ok sthen@ jasper@
instead of firefox-$V/extensions, the location changed in firefox 21.0.
Note that to properly activate a langpack, it seems you still need to
set general.useragent.locale in about:config.. to be investigated.