libevent 1.4.14b.
svn path=/nixpkgs/trunk/; revision=22697
This commit is contained in:
parent
35cbabdab4
commit
80bcec77ec
1 changed files with 22 additions and 3 deletions
|
@ -1,10 +1,29 @@
|
|||
{stdenv, fetchurl}:
|
||||
|
||||
let version = "1.4.14b"; in
|
||||
stdenv.mkDerivation {
|
||||
name = "libevent-1.1b";
|
||||
name = "libevent-${version}";
|
||||
|
||||
src = fetchurl {
|
||||
url = http://monkey.org/~provos/libevent-1.1b.tar.gz;
|
||||
md5 = "ec8dac612aa43ed172f300f396fcec49";
|
||||
url = "http://monkey.org/~provos/libevent-${version}-stable.tar.gz";
|
||||
sha256 = "00b3wih3qpcik6v0qh1406abs2xb954d58ncqwzs8ar2d93ip9mg";
|
||||
};
|
||||
|
||||
meta = {
|
||||
description = "libevent, an event notification library";
|
||||
|
||||
longDescription =
|
||||
'' The libevent API provides a mechanism to execute a callback function
|
||||
when a specific event occurs on a file descriptor or after a timeout
|
||||
has been reached. Furthermore, libevent also support callbacks due
|
||||
to signals or regular timeouts.
|
||||
|
||||
libevent is meant to replace the event loop found in event driven
|
||||
network servers. An application just needs to call event_dispatch()
|
||||
and then add or remove events dynamically without having to change
|
||||
the event loop.
|
||||
'';
|
||||
|
||||
license = "mBSD";
|
||||
};
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue