From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: libevent-2.0.21
Date: Fri, 04 Oct 2013 16:17:00 -0000 [thread overview]
Message-ID: <20131004161726.GA5829@ednor.casa.cgf.cx> (raw)
In-Reply-To: <524ED71E.6010909@tiscali.co.uk>
On Fri, Oct 04, 2013 at 03:56:30PM +0100, David Stacey wrote:
>On 04/10/13 15:15, Christopher Faylor wrote:
>> 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.
>
>I checked before replying - I should have included the links; sorry.
>Both libevent and tmux are present in several major distros:
>http://pkgs.org/search/?keyword=libevent
>http://pkgs.org/search/?keyword=tmux
It's not up to *you* to check before replying, it's up to the OP and
potential packager.
This is now a moot point but I don't want potential packagers to assume
that other people will do their due diligence for them.
cgf
next prev parent reply other threads:[~2013-10-04 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 5:05 libevent-2.0.21 Chris Olin
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 ` Christopher Faylor [this message]
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=20131004161726.GA5829@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.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).