Hey guys,

I hope while you are all at OSCON without me (ok, I'm in a beachfront
hotel in Rio, so I guess it's fair) you can sit down and figure out if
glib is too strong of a depend to require. Not necessarily whether we
should use it in the client programs or in the server, but whether we
_can_ consider/not consider it due to build and installation on OSX.

There is, of course, nothing that glib does that we can't do ourselves,
or use something else for. For instance: libpopt is almost as good as
GOption, and everything can just use getopt_long... although in code
size managed by us to describe the same thing:

 GOption < lipopt < my_getopt < getopt_long

My contention has been that a smaller code base that plays well with and
uses others work can continue to grow and get better as the ecosystem
grows and gets better. Thus my fanatical devotion to deleting mysys and
mystrings (if they're that much better... glibc takes patches I'm sure).

However, I recognize that swapping size of code for size/complexity of
depends/configure/build isn't always the right thing to do...

BUT... due to my absence, here are my thoughts:

I vote for allowing ourselves to use standard linux packages. But
standard, I mean things just about any linux dev could be assumed to
have access to, and anyone else on a UNIX-like system could compile and
install. I'd say to meet the threshold of us using it, it should:

  1- Be in Debian
  2- Be in CentOS
  3- Be in Fedora
  4- Be at the very least COMPILABLE and working on OSX and Solaris

Thus, our use already of libpcre, libevent and readline.

SO....

While you're all together, someone who isn't me please decide if glib
(and other things like it, like apr, or whatever) is too heavy a depend
to bother considering the technical merits or demerits. If it is, I'll
come up with someone else for the things I wanted it for in the clients.
But let's at least have a standard...

Monty


_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help   : https://help.launchpad.net/ListHelp

Reply via email to