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 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
