Posted on 13 Comments

OurDelta builds for MySQL (5.0.67.d6)

With the build system, repos, patches and launchpad sorted, we can release! First up from OurDelta is a build of 5.0.67, using patchrev d6, for i386/x86_64. This is basically Percona patchset 5 with a few fixes plus the Sphinx storage engine. It even passes the testsuite πŸ˜‰

Other useful links:

Now, this being a first release into the wild, there are bound to be some glitches. Most likely in the packaging (and the repo instructions) but possibly also in the builds themselves. Trust comes over time, right? That’s ok, you can help! Simply report any issue using the above bugs link! And please do report success also, although that’s done best through the mailing list or a blog.

In case you’re wondering, 5.1 and beyond are also coming, with more interesting goodies! And you can help! Your first step is to join the mailing list.

A big thanks to everybody involved so far, this was a great team effort! (see the about page for a non-exhaustive list)

Posted on 13 Comments

13 thoughts on “OurDelta builds for MySQL (5.0.67.d6)

  1. Very nice.

  2. nice, love the binaries! Can folks submit patches too?

  3. Yep, just branch from the ourdelta repo trunk, and push to have the patch looked at by others.

  4. Hi,
    I post a comment on mysqlperformanceblog about OurDelta ubuntu repo, think it may be useful:
    http://www.mysqlperformanceblog.com/2008/10/13/perconas-patches-spread-to-a-wider-audience/#comments

  5. Thanks – please do use the proper place for feedback/bugreports, so they won’t get lost. Sticking them in someone else’s blog (or here for that matter) is not good because it might be someone else who needs to look at it, not even me.

  6. Sure,
    I made cross post to https://launchpad.net/ourdelta

  7. Just wonder if we could have the source rpm πŸ™‚

    Try to search in the repo but could not find.

  8. Well, source RPMS get a bit tricky, they’re tied to the build environment we’re using. E.g. you can’t just do a rebuild outside of the environment.

    Patched source tarballs are easy and yes they will appear also.
    I would however encourage people to not work with it as a big branch, but rather use the list of patches that the launchpad repo uses.
    It’s easier to manage and keep track of then, also when you contribute.

  9. Dude, that’s not GPL compliant.

  10. Sorry, what what isn’t?

    (and who are you – it’s nice to know who I’m speaking with – thanks)

  11. β€œThe source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.”

    http://gpl-violations.org/faq/sourcecode-faq.html

  12. Sure. Which is why I said, there’ll be pre-patched source tarballs as that would remove much of the current build-environment dependency.

    However, right now you can still get to the same result. Anybody who downloads the binaries has the right to ask for the sources, which include the ability to rebuild them functionally.

    I appreciate your question, and for sure GPL compliancy is very important.
    However, there is no cause for concern or doubt in this case, unless there’s another aspect you haven’t raised?

    (you’re still anonymous though, pity – I prefer talking with real humans)

Comments are closed.