hi Guys,
There seems to be a bit of interest in making MariaDB available in CentOS-Extras. There are a few options on how we set it up by default:
1) replace MySQL completely 2) Have a parallel install with default port :3307 3) split the package by configs and have a config that replaces mysql, sets port :3306 while the default install is a parallel install ( /var/log/maraidb and port 3307 )
thoughts ?
On Wed, Dec 19, 2012 at 12:33 AM, Karanbir Singh mail-lists@karan.org wrote:
hi Guys,
There seems to be a bit of interest in making MariaDB available in CentOS-Extras. There are a few options on how we set it up by default:
- replace MySQL completely
- Have a parallel install with default port :3307
- split the package by configs and have a config that replaces mysql,
sets port :3306 while the default install is a parallel install ( /var/log/maraidb and port 3307 )
thoughts ?
Fedora people are interested in having mariadb
why not package it for fedora and fedora-epel ?
------------
Itamar Reis Peixoto
On 12/19/2012 03:04 AM, Itamar Reis Peixoto wrote:
why not package it for fedora and fedora-epel ?
is MariaDB suiteable for EPEL ?
On Wed, Dec 19, 2012 at 1:10 AM, Karanbir Singh mail-lists@karan.org wrote:
On 12/19/2012 03:04 AM, Itamar Reis Peixoto wrote:
why not package it for fedora and fedora-epel ?
is MariaDB suiteable for EPEL ?
depends on how its packaged
2) Have a parallel install with default port :3307
centos people can share efforts with fedora, both wants the same.
On 12/19/2012 10:33 AM, Karanbir Singh wrote:
hi Guys,
There seems to be a bit of interest in making MariaDB available in CentOS-Extras. There are a few options on how we set it up by default:
Hello!
The Idea is good, but have you tried MariaDB already?
I have tried it, but I had some major problems so I had to move back to MySQL and that's not 'sooooo' easy. After a 'yum remove mariadb*' I tried 'yum install mysql*', but then yum tried to install mariadb again instead so I have to do some cleanup manually before.
So for example most of my stored procedures are not working. This problem is known there and I have to wait until it's fixed before I will try it again. Another problem is there LGPL-client. Works well with Linux (tested with Fedora 16 and CentOS 6.3 / 32+64 Bit) and Mac OS X, but it don't compile with Windows 7. It's reported from another user already and they have confirmed, that it looks like a bug.
My suggestion is No. 2 but you should wait a few weeks/month more.
And of course, I will try it again as soon there is an upgrade available.
Regards
Guenther
On 12/19/2012 04:33 AM, Karanbir Singh wrote:
hi Guys,
There seems to be a bit of interest in making MariaDB available in CentOS-Extras. There are a few options on how we set it up by default:
- replace MySQL completely
- Have a parallel install with default port :3307
- split the package by configs and have a config that replaces mysql,
sets port :3306 while the default install is a parallel install ( /var/log/maraidb and port 3307 )
+1 for a complete replace. I doubt that anyone would use both servers in the same time on the same machine, except maybe for evaluation purposes. Option 3 is more elegant but I do not think that it's worth the effort
On 12/19/2012 02:51 AM, Manuel Wolfshant wrote:
On 12/19/2012 04:33 AM, Karanbir Singh wrote:
hi Guys,
There seems to be a bit of interest in making MariaDB available in CentOS-Extras. There are a few options on how we set it up by default:
- replace MySQL completely
- Have a parallel install with default port :3307
- split the package by configs and have a config that replaces mysql,
sets port :3306 while the default install is a parallel install ( /var/log/maraidb and port 3307 )
+1 for a complete replace. I doubt that anyone would use both servers in the same time on the same machine, except maybe for evaluation purposes. Option 3 is more elegant but I do not think that it's worth the effort
This is my vote as well.
With respect to EPEL ... if someone wants to do that it would be great. If they do, and if it happens in a timely fashion, we can forgo it in CentOS Extras.
But that is not something we should drive on the CentOS lists.
On Wed, Dec 19, 2012 at 2:51 AM, Manuel Wolfshant wolfy@nobugconsulting.ro wrote:
There seems to be a bit of interest in making MariaDB available in
CentOS-Extras. There are a few options on how we set it up by default:
- replace MySQL completely
- Have a parallel install with default port :3307
- split the package by configs and have a config that replaces mysql,
sets port :3306 while the default install is a parallel install ( /var/log/maraidb and port 3307 )
+1 for a complete replace. I doubt that anyone would use both servers in the same time on the same machine, except maybe for evaluation purposes.
Won't (and shouldn't) that be a problem for any repository with a policy of "don't replace core packages"?
On 19.12.2012 13:48, Les Mikesell wrote:
On Wed, Dec 19, 2012 at 2:51 AM, Manuel Wolfshant wolfy@nobugconsulting.ro wrote:
There seems to be a bit of interest in making MariaDB available
in
CentOS-Extras. There are a few options on how we set it up by default:
- replace MySQL completely
- Have a parallel install with default port :3307
- split the package by configs and have a config that replaces
mysql, sets port :3306 while the default install is a parallel install ( /var/log/maraidb and port 3307 )
+1 for a complete replace. I doubt that anyone would use both servers in the same time on the same machine, except maybe for evaluation purposes.
Won't (and shouldn't) that be a problem for any repository with a policy of "don't replace core packages"?
What they mean is probably to Conflict with mysql, not Obsolete it. A `yum update` won't kill your Mysql.
On Wed, Dec 19, 2012 at 7:52 AM, Nux! nux@li.nux.ro wrote:
There seems to be a bit of interest in making MariaDB available
in
CentOS-Extras. There are a few options on how we set it up by default:
- replace MySQL completely
- Have a parallel install with default port :3307
- split the package by configs and have a config that replaces
mysql, sets port :3306 while the default install is a parallel install ( /var/log/maraidb and port 3307 )
+1 for a complete replace. I doubt that anyone would use both servers in the same time on the same machine, except maybe for evaluation purposes.
Won't (and shouldn't) that be a problem for any repository with a policy of "don't replace core packages"?
What they mean is probably to Conflict with mysql, not Obsolete it. A `yum update` won't kill your Mysql.
So what happens to all of the packages that require mysql clients? Or is the client side compatible?
On 12/18/2012 08:33 PM, Karanbir Singh wrote:
hi Guys,
There seems to be a bit of interest in making MariaDB available in CentOS-Extras. There are a few options on how we set it up by default:
- replace MySQL completely
- Have a parallel install with default port :3307
- split the package by configs and have a config that replaces mysql,
sets port :3306 while the default install is a parallel install ( /var/log/maraidb and port 3307 )
thoughts ?
I think this likely means MariaDB is ready for prime time: http://www.zdnet.com/wikipedia-moving-from-mysql-to-mariadb-7000008912/
hi Guys,
I'm going to try and setup a meetup at Fosdem for the various people interested in MaraiDB/ CentOS to get together and thrash out the details. If anyone has preferences on date/time, please let me know now.
- KB