Re: libevent-2.0.21
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
Re: libevent-2.0.21
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 I forgot to check Cygwin Ports though - libevent is already packaged there, so Yaakov will be able in making this available in Cygwin. http://www.mirrorservice.org/sites/sourceware.org/pub/cygwinports/x86/release/libevent/ http://www.mirrorservice.org/sites/sourceware.org/pub/cygwinports/x86_64/release/libevent/ Dave.
Re: libevent-2.0.21
https://www.archlinux.org/packages/core/i686/libevent/ https://launchpad.net/ubuntu/+source/libevent https://apps.fedoraproject.org/packages/libevent/overview/ http://rpm.pbone.net/index.php3/stat/4/idpl/23404276/dir/centos_5/com/dba-libevent-2021-static-2.0.21-2.1.i386.rpm.html I did understand that part from reading past emails and I don't think it's much of a hoop for this library. I also read about cygport and I'll likely send an actual ITP this weekend, once I familiarize myself with the packaging process and figure out the best way to go about it so it'll be easy to fetch and pull from git and repackage future releases as quick as humanly possible. This was supposed to be the ITP email, but the [ITP] prefix was unexpectedly removed, but it seems to have worked out for the best. On 04/10/13 at 10:15am, 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. If it isn't then we need five votes from package maintainers. cgf
Re: libevent-2.0.21
Didn't see this until after sending my response to Christopher. I'm unfamiliar with Cygwin Ports. If libevent is already available there, is there a process to have it brought into Cygwin so then all that I really need to do is package tmux and send out an ITP? On 04/10/13 at 03:56pm, 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 I forgot to check Cygwin Ports though - libevent is already packaged there, so Yaakov will be able in making this available in Cygwin. http://www.mirrorservice.org/sites/sourceware.org/pub/cygwinports/x86/release/libevent/ http://www.mirrorservice.org/sites/sourceware.org/pub/cygwinports/x86_64/release/libevent/ Dave.
Re: libevent-2.0.21
On 04/10/13 16:07, Chris Olin wrote: Didn't see this until after sending my response to Christopher. I'm unfamiliar with Cygwin Ports. If libevent is already available there, is there a process to have it brought into Cygwin so then all that I really need to do is package tmux and send out an ITP? Please don't top-post. Regarding Cygwin Ports, read the following (short) thread when I asked the same question about a year ago: http://www.cygwin.com/ml/cygwin/2012-10/msg00102.html Essentially, make Yaakov aware that you want to bring a package across from Ports, and that he is happy for you to maintain it. Make sure that you understand the cygport file and any patches that have been applied so that you can keep it (reasonably) up-to-date as new releases come along. Cheers, Dave.
Re: libevent-2.0.21
On 10/4/2013 09:07, Chris Olin wrote: is there a process to have it brought into Cygwin so then all that I really need to do is package tmux and send out an ITP? You can adopt the libevent package yourself, which relieves Yaakov -- who maintains Cygwin Ports -- of the burden of maintaining it. 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, too. That is, if libevent needs some fix or update to allow those packages to continue working, you'll be pressured to fix it even though you do not need the fix yourself for tmux.
Re: libevent-2.0.21
On 2013-10-04 10:07, Chris Olin wrote: Didn't see this until after sending my response to Christopher. I'm unfamiliar with Cygwin Ports. If libevent is already available there, is there a process to have it brought into Cygwin so then all that I really need to do is package tmux and send out an ITP? Done. It should show up on the mirrors shortly, at which point you may proceed with ITPing tmux. HTH, Yaakov
Re: libevent-2.0.21
On 04/10/13 at 04:13pm, David Stacey wrote: On 04/10/13 16:07, Chris Olin wrote: Didn't see this until after sending my response to Christopher. I'm unfamiliar with Cygwin Ports. If libevent is already available there, is there a process to have it brought into Cygwin so then all that I really need to do is package tmux and send out an ITP? Please don't top-post. Regarding Cygwin Ports, read the following (short) thread when I asked the same question about a year ago: http://www.cygwin.com/ml/cygwin/2012-10/msg00102.html Essentially, make Yaakov aware that you want to bring a package across from Ports, and that he is happy for you to maintain it. Make sure that you understand the cygport file and any patches that have been applied so that you can keep it (reasonably) up-to-date as new releases come along. Cheers, Dave. Yeah, I realized I was top-posting after my last email. Mea culpa. Yaakov already posted the announce list re: libevent. I'll work on packaging and sending the ITP for tmux soon and relieve Yaakov of having to maintain libevent, even with Warren's warning in mind. This is all a little bit of unfamiliarity all at once, but I think I'll manage. Might as well throw myself to the wolves for the learning experience. Thanks all.
Re: libevent-2.0.21
On 04/10/13 at 09:15am, Warren Young wrote: On 10/4/2013 09:07, Chris Olin wrote: is there a process to have it brought into Cygwin so then all that I really need to do is package tmux and send out an ITP? You can adopt the libevent package yourself, which relieves Yaakov -- who maintains Cygwin Ports -- of the burden of maintaining it. 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, too. That is, if libevent needs some fix or update to allow those packages to continue working, you'll be pressured to fix it even though you do not need the fix yourself for tmux. To clarify, that would that only apply if other packages dependent on libevent are brought into Cygwin in the future, yes?
Re: libevent-2.0.21
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
Re: libevent-2.0.21
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.)
libevent-2.0.21
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.
Re: libevent-2.0.21
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. You'll need to build it first - a tool called cygport will help you here. I would suggest splitting it into four packages containing runtime binaries, a 'devel' package containing header files and the lib to link against, and a 'doc' package containing the documentation. The fourth package will contain the source code that builds the other three packages. When you're ready, submit an e-mail to this list with the subject line '[ITP] libevent-2.0.21-1'. Here is an example of an ITP message that I submitted recently: http://www.cygwin.com/ml/cygwin-apps/2013-09/msg00222.html If you've not used cygport before then take inspiration from other packages in Cygwin that are split in a similar way. For instance, unpack the poco source file and look at the cygport file therein. Hope this helps, Dave.
