Planet MySQL Planet MySQL: Meta Deutsch Español Français Italiano 日本語 Русский Português 中文
Showing entries 1 to 5

Displaying posts with tag: source code (reset)

Added a Table of Contents
+1 Vote Up -0Vote Down

Not a big deal, but I just added a “Table of Contents” page to my blog to make finding older articles much easier.

I noticed most of my posts are quite lengthy, and it can take a bit of searching/clicking to find an older entry. So unless you happen to recall the ‘month/year’ it was published, which I don’t even remember that, then hopefully this will help.

Really simple, and looks just like this:

  [Read more...]
The MySQL Source is Now Back on Launchpad!
+2 Vote Up -0Vote Down

Last Friday, I had posted that the MySQL Source Code on Launchpad had not been updated (or rather not accessible by Lauchpad) in nearly a month.

I had actually started to file a bug report about this, but when posting the relevant links for documentation, I had noticed new information had been posted yesterday (10/10/2011).

Here was the orignal MySQL Launchpad page:

https://code.launchpad.net/~mysql/mysql-server/mysql-trunk

Here is the new message on this page:

“This is the old MySQL server branch and it is no longer used since mirroring setup has changed.

You can find the development head at https://code.launchpad.net/~mysql/mysql-server/trunk instead.”

If you navigate to the new page:

  [Read more...]
Where’s the Updated MySQL Source Code on Launchpad?
+8 Vote Up -0Vote Down

I know I’m not the only one to have noticed that all MySQL branches on Launchpad have not been accessible since September 10th, 2011, nearly 1 month.

Just visit here:

https://code.launchpad.net/~mysql/mysql-server/mysql-trunk

You’ll see it says:

“This branch may be out of date, because Launchpad has not been able to access it since 2011-09-10.”

I’d been seeing “No revisions to pull.” messages latley, when running “bzr pull”, but didn’t give it a whole lot of thought until reading the above note on Launchpad today.

Is it due to the recent security breach (where mysql.com was hacked and infected some visitors with malware)? Well, I doubt it since this started on 9/10/2011 and the breach, according to The Register, occurred on 9/26/2011 (some

  [Read more...]
Bug When Compiling MySQL 5.1 From Source
+0 Vote Up -0Vote Down

I just filed a very annoying bug when trying to compile with plugin engines using the 5.1.xx source tarball.

Description

I am trying to test SphinxSE as a plugin instead of getting it statically linked and came across an annoying bug. When using the configure --with-plugins option only once, the engine is statically linked. When using it twice, the first engine is created as a plugin, and the 2nd one is linked statically. Here are a couple of examples:./configure –prefix=/usr/local/mysql-5.1.33 –with-plugins=innobase –with-plugins=sphinx

plugin_innobase_shared_target='ha_innodb.la'   <-- plugin
plugin_innobase_static_target=''
plugin_sphinx_shared_target=''
plugin_sphinx_static_target='libsphinx.a'       <-- static
  [Read more...]
Changing MySQL’s Community Contribution Agreement
+0 Vote Up -0Vote Down

A while ago, MySQL developed a Community Contribution Agreement for community contributions to the MySQL source code. While browsing the MySQL Forge Wiki I came across:

http://forge.mysql.com/wiki/Community_Contributions

This page shows that the Community Contribution Agreement has changed — it is no longer the document MySQL AB created. It is now Sun Microsystem’s standard Sun Contributor Agreement, which CEO Mårten Mickos recently explained to me was “more accepted than the agreement MySQL had come up with.”

I am happy to see some of the great Sun practices trickle down to replace some issues that MySQL did not handle smoothly. All in all, I agree with Mårten Mickos and think the Sun Contributor Agreement is much better….

….but what do you think?

Showing entries 1 to 5

Planet MySQL © 1995, 2014, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.