Actually there is this: https://bugs.launchpad.net/drizzle/+bug/823272 "Offer binary tar for download"
However, offering RPMs and DEBs is more important. Until this email thread I assumed RPMs and DEBs would continue to appear magically so I'm not aware of a blueprint or bug about that topic. I'm happy to write one if it makes it more likely that 7.1 beta will be released with RPMs and DEBs. In any case, the contents of such a blueprint would be: *** Overall requirement: Drizzle releases should always include RPM and DEB formats. (And preferably but less critically also binary TAR, see separate bug about that.) Implementation requirements: The code, scripts and spec files needed should be included in main drizzle bzr repository. This means it is possible to do "make rpm" and "make deb" from the drizzle sources. Building RPM and DEB formats should be included as Jenkins build targets and included in integration test for new patches coming into trunk. Primary way of building RPM and DEB is from the source TAR package, not directly from bzr. (ie these need to be chained Jenkins jobs.) Jenkins QA of these packages should start from a clean Centos/Ubuntu/Debian VM to ensure that RPM/DEB dependencies are correctly defined. Other Jenkins tests can include things like upgrading from Drizzle 7, or installing Drizzle into a Linux where default distro version of MySQL is already installed. An important use case (that I recently added to the top level Drizzle README) is that you should be able to compile Drizzle from source after doing apt-get build-dep drizzle. This should be a separate test too. (Ie if developer adds dependencies on new libraries, they need to fix DEB/RPM to include that dependency.) **** I did this kind of stuff for DEBs and binary TARs in my paternity leave "MepSQL" project, so I'm happy to help out if you need more hands. As I see it working on better documentation is a lost cause if we don't offer friendly installation packages first. henrik On Fri, Sep 30, 2011 at 1:34 AM, Mark Atwood <[email protected]> wrote: > Are there blueprints or open bugs about adding build targets? > > On Wed, Sep 28, 2011 at 7:34 PM, Brian Aker <[email protected]> wrote: >> >> That is up to the packagers. I'd really like to see them become build >> targets. >> >> Sent from my TI85 >> >> On Sep 27, 2011, at 23:19, Henrik Ingo <[email protected]> wrote: >> >>> Btw, does beta status mean that there will be RPMs and DEBs, or is it >>> still source only? (I'm of course asking because I'm hoping for the >>> former, it's very important for adoption to provide packages.) >>> >>> henrik >>> >>> On Fri, Sep 23, 2011 at 7:19 PM, Brian Aker <[email protected]> wrote: >>>> >>>> Stewart, Patrik, and I met up in person today. To get the beta out the >>>> door >>>> Crews is going to enable the replication testing for multi-master. >>>> >>>> Other then that? >>>> >>>> Beta is the release after next week. >>>> >>>> >>>> Sent from my TI85 >>>> >>>> _______________________________________________ >>>> 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 > > -- [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
