Ah sorry, I just asked a question and didn't read all my emails to find out you already answered it.
Anyway, in the other thread I outlined a proposal where libdrizzle releases would still mostly coincide and use same versions as the server (while also providing lp:libdrizzle for people that want to build from source). Yeah, we can do it also the other way: not package libdrizzle in lp:drizzle related packages. To me this sounds messy, but it depends on what we need/want from lp:libdrizzle. henrik On Fri, Feb 10, 2012 at 5:17 AM, Brian Aker <[email protected]> wrote: > Hi, > > We could choose to not install the version of libdrizzle that we ship with > the server. Or,... put it into a different directory on install.... > > Cheers, > -Brian > > On Feb 3, 2012, at 4:42 AM, Henrik Ingo wrote: > >> Ah. Turns out this isn't feasible. Of course if using just one spec >> file, all packages coming out of it will end up with the same version >> number. >> >> So we can: >> >> - separate libdrizzle packaging completely. This is problematic >> because when installing the server you'd want to install the client >> too. Otoh if installing from a yum/apt repo it doesn't matter, it's >> just complexity for us when building and testing. >> >> - keep libdrizzle and drizzled together and make them use same >> version number. If there is a need to do libdrizzle releases more >> frequently than the server, it is possible to do a release that >> contains just libdrizzle. However, the next server release would then >> have to skip a build number. >> >> >> I have to think about it. I suppose at this point we should question >> whether we really need to do independent libdrizzle releases? If we >> continue releasing the server once a month, isn't that enough? Or is >> it a problem to release also the server more frequently if there's a >> need for a libdrizzle release? >> >> Seems like giving up on independent libdrizzle releases would solve >> many problems. (There could still be a tarball from where you can make >> libdrizzle without the server, just that the version numbers would be >> strictly coupled.) >> >> henrik >> >> >> >> On Wed, Feb 1, 2012 at 4:24 PM, Henrik Ingo <[email protected]> >> wrote: >>> Hi Brian >>> >>> I was thinking about how to package the libdrizzle breakout >>> (lp:libdrizzle) for rpms and debs. >>> >>> It occured to me the simplest answer is to not do it at all. At least >>> to start with. Since the master repo will still remain at lp:drizzle, >>> we could choose to just provide rpm and deb updates when there is a >>> complete new drizzle release. Interim libdrizzle releases, should they >>> occur, would be source only. >>> >>> This allows us to simply continue using the rpm and deb packaging >>> that's already approved for merging. They already produce a separate >>> libdrizzle rpm/deb (as part of the whole build). >>> >>> 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 >> >> >> >> -- >> [email protected] >> +358-40-8211286 skype: henrik.ingo irc: hingo >> www.openlife.cc >> >> My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 > > > -----BEGIN PGP SIGNATURE----- > > iQEcBAEBAgAGBQJPNIxDAAoJEItO41/aJIgTtxoIAN9E27Ndn2V4w8s9d3uA+Zro > TkBAGM0th/6jpiSoj/68Lkpu6OjDlVCLVwZfXveYO0fQqF+zoX0iRbTuj6dpwr/W > VGxNPrwKa1n3hwz/FhMm6vORfLDCLw1etfFQtUabhzVBTmhao29KFNJgtlce1W2E > 2aVU5blwafNK49lhWfcbY19ATDMwhtwI1v5qHlI31YYJ/F5SpGeqMx+nfXB23nMp > dqLhK5jQLQfBHNt5KgtblGLADSv4E8TxiMMzRBv1+rBQZhPeWJAea48ASuIH013h > t9p6Xj4+KZezJtMf1TkgAXyedvLG/QAMJ1opXX7CsQJ2RsZtWi13jTWb6X1JslA= > =1oyr > -----END PGP SIGNATURE----- > -- [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
