This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: libevent-2.0.21
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Fri, 4 Oct 2013 10:15:53 -0400
- Subject: Re: libevent-2.0.21
- Authentication-results: sourceware.org; auth=none
- References: <CAJ3eT+-Ff=x9cWUOU6WBjUfOJ1tp8A121wOxuTa8VJJSq4985g at mail dot gmail dot com> <524E5624 dot 2080206 at tiscali dot co dot uk>
- Reply-to: cygwin-apps at cygwin dot com
On Fri, Oct 04, 2013 at 06:46:12AM +0100, David Stacey wrote:
>On 04/10/13 06:05, Chris Olin wrote:
>> Bear with me, as this is my first time doing this and every archived
>> intent email seems to have it's own format. Any advice is appreciated.
>>
>> category: Libs
>> sdesc: "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."
>> ldesc: "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. "
>> requires: ncurses-devel
>>
>> http://libevent.org
>
>If you're offering to maintain a package then thank you.
Ditto but there is at least one more hoop to jump through before the
package is even accepted into the distribution. You have to show that
it is available in major Linux releases first. If it isn't then we need
five votes from package maintainers.
cgf