Hi Brian Did you figure out what to do with versioning and such?
The more I think about it, the more I went back to the idea that when it comes to packages, libdrizzle could continue to be released together with drizzled, and only that. After all, the original request was for someone who wanted to compile libdrizzle from source, and that is now satisfied. So my proposal is we provide: - if you want to build both drizzled and libdrizzle, you can use lp:drizzle and also drizzle-7.1.z.tar.gz - if you want to build only libdrizzle, you can use lp:libdrizzle. There is no source tar release. Note: If you plan to do tar ball releases, please share how you intend to version them. - if you want libdrizzle binaries only, you can install libdrizzle rpm or deb. These releases concur with server releases and the packages will have the same 7.1.z version numbers. Note: same is true for binary tars, if we ever provide them. There could easily be a separate libdrizzle binary tar, but it would have the same version number and coincide with a server release. - if there is a need to do a libdrizzle release (using the above method where server is build but deleted) to provide some hotfix while not releasing the server, there are 3 options: - No release, just ask the customer to pull lp:libdrizzle - Make a libdrizzle only release from the lp:drizzle release system. Delete server binaries that were produced. This will consume a build number, so the next server release would skip a beat in the third digit. - Make a libdrizzle only release but don't tag a new release number. This will produce a 4 digit snapshot release: [lib]drizzle-7.1.31.2512-snapshot.tar.gz. The benefit is that the next server release would continue without skipping numbers, like from 7.1.31-rc -> 7.1.32-rc. I would advocate for using snapshot releases for libdrizzle only releases. Would these alternatives work for everyone, or you have something else in mind completely? What I write above will work with our current pandora-build. Some other schemes might be nice, but not supported currently by how we actually do releases. henrik On Fri, Feb 10, 2012 at 5:09 AM, Brian Aker <[email protected]> wrote: > Hi! > > lp:libdrizzle lives again! > > It is just a pull from the lp:drizzle that has been chopped down. The plan is > to maintain it for folks who just want libdrizzle. > > Cheers, > -Brian > -----BEGIN PGP SIGNATURE----- > > iQEcBAEBAgAGBQJPNIpgAAoJEItO41/aJIgTbnoIAMcCEK6/oikORW+lIh47KXvG > 9OiyB/D8xxuIXfJc6o7QIt6u43rKCg6YULhZFc7YgMHAnMC44oxTbThwQ2TGYjU5 > jxSv/1MU7FGZCWEmsmtQC/RaFXKjOfIDfidrHqe/2I3LZ8ZiiItPIUS/WYeApfta > MVrGJsmsmkIW19ZcgSCI46ATnch4IoG4yJL3xScNaKOuImzJgF6x/ZNK96piXJMS > 9uaVeIql7vgwDUCA/pJKs9Gah7v+a6jk/pG5EXclSTj+Ecm6jMoQAAVO4XAphh1k > DVbKBZ2UiObjQcFlW9MkMN7iyEZwkPoVTK9ylYNPil+5qOPXor1bot9It1S6H34= > =7X+e > -----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
