Hi all Mark asked yesterday on IRC about the status on RPM and DEB packaging. Here's the status now:
I had already sent a merge proposal for branches for both make deb and make rpm. However, those where from before we fixed the versioning to current drizzle-7.1.31-rc style. Those branches won't merge against trunk today, and wouldn't be correct anyway. I've deleted them. I had already started working on updating the packaging code to work against what was now merged to trunk. I have published it today: lp:~drizzle-developers/drizzle/drizzle-7.1-packaging This is not yet usable. The major other thing that needs fixing is to remove libdrizzle from that packaging and instead package libdrizzle from the lp:libdrizzle repository, using 1.0.x version numbers. This will allow - making independent libdrizzle releases as needed, - from a distro perspective it will no longer be the case that when you upgrade to different server version, you'd also have to upgrade/uninstall/recompile every package that depends on libdrizzle. (Paradoxically, this could be expressed as "allows making less libdrizzle releases".) I created a blueprint to track the status. https://blueprints.launchpad.net/drizzle/+spec/7.1-packaging see also http://bazaar.launchpad.net/~drizzle-developers/drizzle/drizzle-7.1-packaging/view/head:/support-files/README So unfortunately it seems this will miss the 7.1 RC, but it's not a biggie, the plan now is to maintain a parallel repo (see above) through the 7.1 series, which we could still point Jenkins at. Then as soon as 7.2 series starts we can hope to get this in again. (It could be argued that since this doesn't touch any code, except Makefile and configure just a little, that it could even be merged into 7.1 post RC. I usually like to follow the rules so I won't make that argument, but also won't oppose it, if it would happen.) As usual, any help in attacking the bullet points from the blue print is of course always appreciated. Bear in mind there are 4 different dimensions for this problem: - Debian: DEB packages, sysv init script - Ubuntu: DEB packages, upstart script - RHEL/Centos/Fedora: RPM packages, sysv init script - Fedora 16: RPM, systemd init script (I'm not really focusing on Fedora 16 just yet. Fedora can blame themselves for introducing broken system) Since I only work on one of the above at any given time, it means solving the complete problem will take weeks if working alone. 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
