Bug#647740: ITP: libvertfo - library abstracting event loop interfaces

2011-11-06 Thread Sam Hartman
OK, so I had not looked at what this does on win32. I think any
criticism you have of the libverto win32 interface is probably valid.
Fortunately I don't think that's being used.



-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/tslwrbdkwr9@mit.edu



Bug#647740: ITP: libvertfo - library abstracting event loop interfaces

2011-11-06 Thread Ben Hutchings
On Sat, 2011-11-05 at 13:34 -0400, Sam Hartman wrote:
> package: wnpp
> severity: wishlist
> 
> URL: https://fedorahosted.org/libverto/
> Description: libverto provides a common interface on top of libev,
> libevent, glib, tevent.
>   The goal is to allow development of asynchronous libraries that
> will work with whatever event loop an application happens to be using
>   Features include automatic detection of which event loops are in a
> particular process space and support for writing new event loop
> modules.

It appears that 'work with' means 'sneakily insert itself into' and
'automatic detection' means 'dubious hacks'.  What could possibly go
wrong?

[...]
> I'm packaging this because it's a dependency for MIT Kerberos 1.10.
[...]

Then MIT Kerberos appears to be doomed.

Please point your upstream at:
https://git.kernel.org/?p=linux/kernel/git/kay/libabc.git;a=blob_plain;f=README
http://blogs.msdn.com/b/oldnewthing/archive/2005/02/14/372266.aspx

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?


signature.asc
Description: This is a digitally signed message part


Bug#647740: ITP: libvertfo - library abstracting event loop interfaces

2011-11-05 Thread Sam Hartman
package: wnpp
severity: wishlist

URL: https://fedorahosted.org/libverto/
Description: libverto provides a common interface on top of libev, libevent, 
glib, tevent.
  The goal is to allow development of asynchronous libraries that  will work 
with whatever event loop an application happens to be using
  Features include automatic detection of which event loops are in a particular 
process space and support for writing new event loop modules.

License:
 * Copyright 2011 Red Hat, Inc.
 *
 * Permission is hereby granted, free of charge, to any person
 * obtaining a copy of this software and associated documentation files
 * (the "Software"), to deal in the Software without restriction,
 * including without limitation the rights to use, copy, modify, merge,
 * publish, distribute, sublicense, and/or sell copies of the Software,
 * and to permit persons to whom the Software is furnished to do so,
 * subject to the following conditions:
 *
 * The above copyright notice and this permission notice shall be
 * included in all copies or substantial portions of the Software.
 *
 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
 * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
 * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
 * NONINFRINGEMENT.  IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
 * BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
 * ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
 * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 * SOFTWARE.


I'm packaging this because it's a dependency for MIT Kerberos 1.10.
It's kind of annoying but libverto has not yet been released so I'll
probably end up packaging a git snapshot. I'll prod upstream and see
if a release can be caused to happen.



-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/2005173408.0b7a14...@carter-zimmerman.suchdamage.org