Le vendredi 25 janvier 2013 à 19:05 +0100, Reindl Harald a écrit :
Am 25.01.2013 18:57, schrieb Rahul Sundaram:
> Just to be clear, RHEL != Fedora. Red Hat policy for RHEL kernel is not acceptable
to Fedora and Fedora kernel
> continues to have the patches split out. You cannot use that to defend MySQL
policies here. You can do whatever
> you want to do for the MySQL "enterprise edition" which is a commercial
product but the community project should
> have transparency and openness in how it handles bugs, security issues, test cases
etc. If you are willing to
> commit to that, that is a step forward.
this is all nice and fine
but keep in mind that Fedora is the base for RHEL
applications may be certified for mysql
If you take a look at the RHEL channels, you will see that RH is
perfectly able to offer packages not coming from Fedora and to support
them ( exemple, passenger for openshift, or jboss, cloudforms ). And
Oracle can perfectly offer mysql rpms for Fedora if you need them.
And again as Rahul said, RHEL != Fedora.
If the Fedora Mysql maintainer all think this is too time consuming to
keep Mysql in Fedora , then he is right. We should keep the
sustainability in mind, or that's the recipe for long term problems.
and yes you are unsopported to run them at all on Fedora
but run them additionally on a fork of mysql which maybe
more and more incompatible over the years you are out of
hope and have not anything from the subjective freedom
if there is no way to have both, mysqld AND mariadb Fedora
should do itself a favour and keep mysqld, not for now -
forever or as long not most other software supports mariadb
explicitly which is not the case now
No one is going to support mariadb explicitly unless it start to be
distributed widely.
And instead of spreading FUD, please take a look at smaller distribution
that did switch to mariadb ( for example, mageia, who did since more
than 1 year ). Ask them if this cause problems or not, if they have lots
of unsupported softwares, etc.
Then you will be able to claim "this is not supported". From what I
know, the switch was handled without problem.
--
Michael Scherer