On Sat, Dec 10, 2011 at 3:25 PM, Olaf van der Spek <[email protected]> wrote: > Hi Brian, > >> Update all of libdrizzle per mine and Mark's conversation about how to break >> out code from interface. > > Where was this discussed? I don't remember seeing it on the list.
+1 Could someone please update us Europeans on the state of the client plus libdrizzle versions. I was going to add back the [drizzle|mysql]_password_hash code as discussed in another thread, but I got unsure what the intention is currently, so decided to ask first... In the source I see: libdrizzle/ - this is code of libdrizzle-1.0 separated out libdrizzle-1.0/ - this is the libdrizzle.1 api, will use the implementation code in libdrizzle/ libdrizzle-2.0/ - this is as before, both an api and implementation. - this is currently not part of make install and hence will also not be part of any packages. client/ - the drizzle client and other utilities. These otoh still build against libdrizzle-2.0 Main point of confusion is whether it is intentional that the clients build against libdrizzle-2.0, and if it is, what is the rationale for doing that? If I want to add mysql_password_hash.cc functionality into the client, I need to know whether that should be in libdrizzle-1.0, libdrizzle-2.0 or perhaps just the client itself? (Come to think of it, it could also be a client plugin...) henrik -- [email protected] +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
