On Fri, 25 Jan 2013, Honza Horak wrote:
On 01/23/2013 01:04 PM, Ales Kozumplik wrote:
On 01/22/2013 10:06 PM, Tom Lane wrote:
Yes, that's the general idea --- any dependencies on mysql should result
in installing mariadb, unless the user takes specific action to get
mysql instead. Ideally we'd just do the standard Provides/Obsoletes
dance for replacing one package with another, but I'm not quite sure how
that should work if we still want original mysql to be installable. Any
thoughts from RPM experts would be welcome.
I'm not an RPM expert, yet if mariadb obsoletes mysql and mariadb is
installed then specifically selecting mysql package for installation
will not be possible (because it is obsoleted).
This is true, switching back to mysql wouldn't be easy for users. I haven't
tested this one yet, but I guess they will be able to do it in two steps:
* remove all mariadb packages
* install mysql with excluding mariadb explicitly
A bad thing is, that they will have to re-install even other depended
packages, which have been removed during mariadb removal.
Is there really no way to do removal/install like above in one yum
transaction?
yum shell
remove foo
install bar
run
-sv
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
