take a stronger stance and remove evutil_secure_rng_add_bytes() from
libevent's API. Nothing calls it anyway, and there's even a big scary
warning (tm) in libevent's header..
---
You should almost never need to call this function; it should be
sufficient to invoke evutil_secure_rng_init(), or let Libevent take
care of calling evutil_secure_rng_init() on its own.
If you call this function as a _replacement_ for the regular
entropy sources, then you need to be sure that your input
contains a fairly large amount of strong entropy. Doing so is
notoriously hard: most people who try get it wrong. Watch out!
---
Bump event_core major, and remove the now useless configure.in patch.
Discussed with/ok sthen@
old-time and time. After comparing all the .hi files before and
after (using ghc --show-iface) I guess this changes had been triggered
by the suseconds_t change some weeks ago (my previous ghc build was
from october 23rd, so just a little bit before that change).
People following -current and using Haskell for serious work should
wait with updates until the new ghc and hs-packages are built and
copied out to the mirrors. Any Haskell additional libraries built
manually (i.e. using cabal something) should be rebuilt. If in
doubt, run ghc-pkg check to see if anything is broken for you.
Fixes this problem (notified by sthen):
Use of uninitialized value in pattern match (m//) at
/usr/local/libdata/perl5/site_perl/Net/Server.pm line 600.
From sthen:
one of the tests fails if you have IO::Socket::SSL installed (it tries to run a local ssl
server and connect to it but fails due to it being an unknown ca, IO::Socket::SSL defaults got
tighter) but that isn't new and isn't a real problem
ok sthen, gonzalo
Jingle support in kopete-4.11.3. The kdenetwork-4.10.5 could also use it
for the same thing, but my tests showed that Jingle doesn't work there, so
no point in enabling it.
oRTP - a Real-time Transport Protocol (RFC3550) stack under LGPL.
It implements the RFC3550 (RTP) with a easy to use API with high and
low level access and features:
* Support for multiples profiles, AV profile (RFC3551) being
the one by default.
* A packet scheduler for sending and recieving "on time", according
to their timestamp. Scheduling is optionnal, RTP sessions can remain
not scheduled.
* Mutiplexing I/O, so that hundreds of RTP sessions can be scheduled
by a single thread.
* Adaptive jitter algorithm for a receiver to adapt to the clockrate
of the sender.
* Supports part of RFC2833 for telephone events over RTP.
* The API is well documented using doxygen.
* RTCP messages sent periodically since 0.7.0 (compound packet
including sender report or receiver report + SDES).
* An API to parse incoming RTCP packets.
okay landry@
The Link Grammar Parser is a syntactic parser of English, Russian,
Arabic and Persian (and other languages as well), based on link
grammar, an original theory of English syntax. Given a sentence,
the system assigns to it a syntactic structure, which consists of
a set of labelled links connecting pairs of words. The parser also
produces a "constituent" (Penn tree-bank style phrase tree)
representation of a sentence (showing noun phrases, verb phrases,
etc.). The RelEx extension provides dependency-parse output.
okay landry@, espie@ (for the BUILD_PACKAGES part)
committed upstream. It already works in mandoc(1), and it is used in
some OpenBSD base system manuals, and using it is generally encouraged,
so having it in our groff port as well really makes sense.
ok bentley@ on August 1, 2013 (and i forgot to commit after unlock, sorry)
