> If we want to use a different name, I would want to have that discussion off > list so that we can grab the .org/.com before some enterprising individual > does (I am happy to pay for it and just assign it over to the foundation).
Yes, it's known to happen... I don't think this is about the name though, more like it's about the version number. I understand Clints suggestion that we should strive to build packages where libdrizzle version number is independent. Currently: drizzle_7.1.31.-rc-1_i386.deb drizzle-client_7.1.31-rc-1_i386.deb drizzle-dbg_7.1.31-rc-1_i386.deb ...etc... libdrizzle1_7.1.31-rc-1_i386.deb libdrizzle-dbg_7.1.31-rc-1_i386.deb libdrizzle-dev_7.1.31-rc-1_i386.deb Should become drizzle_7.1.31.-rc-1_i386.deb drizzle-client_7.1.31-rc-1_i386.deb drizzle-dbg_7.1.31-rc-1_i386.deb ...etc... libdrizzle1_1.0.x-1_i386.deb libdrizzle-dbg_1.0.x-rc-1_i386.deb libdrizzle-dev_1.0.x-rc-1_i386.deb I support the idea that lp:drizzle must be the canonical home of the libdrizzle code, because there will be times when you make changes both on the server and client side. Otoh, to de-couple version numbering, we need to build libdrizzle separately, this could then happen in lp:libdrizzle. (It could also happen by just maintaining a separate .spec file and debian/ directory inside lp:drizzle that is used to build libdrizzle packages.) If you just do make install in lp:drizzle, it would do pretty much what it does now. IMO it is only good if the outcome of that is the same as doing make install in libdrizzle. I never understood what potential problems you see if people install libdrizzle via lp:drizzle versus lp:libdrizzle? Shouldn't the output be identical? *** There's one more thing though. For the libdrizzle version numbers, it would now be natural to use the version number from configure.ac. However, for the variant known as libdrizzle-1.0, this is currently 2.x.x! condigure.ac: OLDLIBDRIZZLE_LIBRARY_VERSION=2:0:1 If I were to use that number, we would end up with packages named "libdrizzle1" with version 2.0.1 and contents from libdrizzle-1.0/ not libdrizzle-2.0/ This is actually confusing me a little - I hesitate to use a 2.x.x version since there is a different code base known as 2.0. I understand I can't bump the configure.ac version down to 1.0 either. The next available version would be 4.0.0 because 3.x.x was also already used. Yeah, I need advice on that one... henrik On Sun, Feb 12, 2012 at 12:20 PM, Brian Aker <[email protected]> wrote: > Hi, > > Would it make sense to ship libdrizzle in its standalone form as > "libdrizzle-client",... > > Or something entirely different, but related? > > It does have some, though it needs to be developed more, support for other > databases as well. > > I would like for the code in lp:drizzle to be the canonical source, but the > end result of "lp:libdrizzle",... we can change its name to avoid some of > these issues. > > Thoughts? > > If we want to use a different name, I would want to have that discussion off > list so that we can grab the .org/.com before some enterprising individual > does (I am happy to pay for it and just assign it over to the foundation). > > Cheers, > -Brian > > On Feb 10, 2012, at 1:54 AM, Clint Byrum wrote: > >> The libraries on a system are a lot harder to get right than a single >> daemon, so I'd rather see libdrizzle be its own stable, barely changing >> thing. This way if somebody wants the next GA of drizzled in 2 years on a >> system which releases with the current GA.. they just have to backport >> drizzled, without concern for messing up anything they've compiled >> against the library. >> >> Right now we can't ship backports of mysqld easily in Ubuntu backports, >> because it requires testing all of the reverse depends of libmysqlclient. >> In order to do a backport, one has to remove libmysqlclient from the >> installation, which is not as easy as it sounds since the client programs >> link against it. > > > -----BEGIN PGP SIGNATURE----- > > iQEcBAEBAgAGBQJPN5JuAAoJEItO41/aJIgTeyIIAKL0WUw2taJD965cwmQKAhCb > ql/OM9g72KS99NOGP/t/kns1IR2RB4lqjjBorQ9Y2YrDRqfkNaHZLao+uGg6/qjc > OHIwTk2U6tN+dsIRfyFP011cGiC3Lqeo4gWHfaAYCJZ1otNpMBGf5CgItjt6JXZe > bIaz/d000pn1epP70I2RbvapWATkzqP80s1KFNFFwW2X0MH7p0qRGxVnvOLZI2H/ > bK6zHkzPLABIomdQFG+KWjCpy5i+T+/NNoSJQ25sQ2pqcWLgDGJmrLSphFDDew2/ > f6hld6HwfuEgUfQhYx+O87cY0RDiRIst6q9KpElfe++brTBrkeb/of63thd44sc= > =hnfc > -----END PGP SIGNATURE----- > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp > -- [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
