public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Chris Olin <chris@chrisolin.com>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: libevent-2.0.21
Date: Fri, 04 Oct 2013 05:05:00 -0000	[thread overview]
Message-ID: <CAJ3eT+-Ff=x9cWUOU6WBjUfOJ1tp8A121wOxuTa8VJJSq4985g@mail.gmail.com> (raw)

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

It stands to reason that I should mention that plan on declaring my
intent to maintain tmux next if this intent is accepted, which
requires this library to function. Both can be successfully built from
source without any patching, but requires ncurses.h, which ins
included in the ncurses-devel package.

I couldn't find any archived ITPs for any libraries or any
documentation that said otherwise. If there's another/better way of
approaching this, please let me know.

             reply	other threads:[~2013-10-04  5:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04  5:05 Chris Olin [this message]
2013-10-04  5:46 ` libevent-2.0.21 David Stacey
2013-10-04 14:15   ` libevent-2.0.21 Christopher Faylor
2013-10-04 14:56     ` libevent-2.0.21 David Stacey
2013-10-04 15:05       ` libevent-2.0.21 Chris Olin
2013-10-04 15:14         ` libevent-2.0.21 David Stacey
2013-10-04 15:38           ` libevent-2.0.21 Chris Olin
2013-10-04 15:15         ` libevent-2.0.21 Warren Young
2013-10-04 16:10           ` libevent-2.0.21 Chris Olin
2013-10-04 18:39             ` libevent-2.0.21 Warren Young
2013-10-04 15:24         ` libevent-2.0.21 Yaakov (Cygwin/X)
2013-10-04 16:17       ` libevent-2.0.21 Christopher Faylor
2013-10-04 15:02     ` libevent-2.0.21 Chris Olin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ3eT+-Ff=x9cWUOU6WBjUfOJ1tp8A121wOxuTa8VJJSq4985g@mail.gmail.com' \
    --to=chris@chrisolin.com \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).