Hi!
Thanks for the input from everyone. It sounds like the best path
would be to make libevent support an optional feature. I've created a
blueprint here (please add any features I missed):
https://blueprints.launchpad.net/drizzle/+spec/new-client-lib
I also pushed a new branch with the build integration and a first
pass at a public header file (in libdrizzle.new/drizzle.h):
lp:~eday/drizzle/new_client_lib
It will still change, but any feedback on the design thus far would
be much appreciated.
-Eric
On Jul 25, 2008, at 10:05 PM, Jesse Vincent wrote:
On Jul 25, 2008, at 9:03 PM, Eric Day wrote:
Hi!
Question for the group: How much do we care about external
dependencies for the client library? For example, libevent is
already being used in the server, and there is certainly room to
use this in the client code. I don't expect many other external
non-core dependencies (if any), but I was curious if the "use
common OSS libs as much as possible" rule applies to the client
lib as well. The reason we may want to keep it dependency free is
if it ends up being built on other systems than the server
supports (like windows, but libevent does work there too).
As a user and packager of database client libraries, I'd like to
humbly beg for making any external dependency in the client library
optional. Adding a single dependency can make life hellish. Adding
a second one can make it doubly hellish. Past that, the battle is
lost and you can include as many as you'd like.
Best,
Jesse
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
