Yum plugin for prioritize providers [was Re: Fwd: MariaDB replacing MySQL]
Norvald H. Ryeng
norvald.ryeng at oracle.com
Wed Mar 20 15:48:33 UTC 2013
On Tue, 19 Mar 2013 08:56:04 +0100, Honza Horak <hhorak at redhat.com> wrote:
> On 03/18/2013 07:17 PM, Bill Nottingham wrote:
>>> I'm not following the MySQL/mariadb packaging discussion in full
>>> >detail - however, if we got to the point of discussing special yum
>>> >plugins, wouldn't it be much simpler to
>>> >
>>> >* Modify the 10 packages that require mysql-server, the 19 packages
>>> >that require mysql, the 3 packages that require mysql-libs (all F18
>>> >counts) to require mariadb-* explicitly instead of using the virtual
>>> >provide
>>> >
>>> >* Make sure that only mariadb-libs, not Oracle MySQL, Provides: the
>>> >libmysqlclient soname?
I would like non-conflicting libraries as well.
>>> >That's about 35 packages to touch, and all but one of them trivial
>>> >modifications.
>> This does sound much simpler, IMO.
>
> It does, but it would be hard to install MySQL in case any package
> requries mariadb, since the two packages conflict. And making the
> packages non-conflicting doesn't seem so simple -- it would mean to
> change location of the binaries or change their file-names, which would
> mean quite a lot of patching. But generally, if we find a way how to
> make the packages to be usable and non-conflicting, it could work fine.
I would also like to have non-conflicting packages. I don't think changing
the names of the binaries would be that much work, but there are config
files, scripts that refer to the binaries, etc. It's some work, but I
think it's doable. And it would solve much of our headache. At least, I
think it's worth considering.
Regards,
Norvald H. Ryeng
More information about the devel
mailing list