public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <warren@etr-usa.com>
To: Cygwin Apps List <cygwin-apps@cygwin.com>
Subject: Re: libevent-2.0.21
Date: Fri, 04 Oct 2013 18:39:00 -0000	[thread overview]
Message-ID: <524F0B5C.5090902@etr-usa.com> (raw)
In-Reply-To: <20131004161242.GD32419@spock.chrisolin.com>

On 10/4/2013 10:12, Chris Olin wrote:
> On 04/10/13 at 09:15am, Warren Young wrote:
>>
>> libevent is in Cygwin Ports to satisfy cyphertite, ocaml-libevent,
>> and transmission.  So, before adopting it, think about whether you
>> want to place yourself in a blocking position for those packages,
>
> To clarify, that would that only apply if other packages dependent on
> libevent are brought into Cygwin in the future, yes?

No.  If you were to adopt libevent, Yaakov would be able to remove it 
from Cygwin Ports, because those packages could then use the "official" 
libevent pacakge.  (i.e. yours.)

  reply	other threads:[~2013-10-04 18:39 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             ` Warren Young [this message]
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=524F0B5C.5090902@etr-usa.com \
    --to=warren@etr-usa.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).