← Back to team overview

maria-discuss team mailing list archive

Re: mariadb-backup meta deb package


Am 14.02.2018 um 12:56 schrieb Florent B:
On 14/02/2018 12:49, Sergei Golubchik wrote:
Hi, Florent!

On Feb 14, Florent B wrote:

Wouldn't be nice to have a metapackage mariadb-backup in Debian
repository, that depends on the current best version
(mariadb-backup-10.2, etc..) ?

Like "mariadb-server" package in fact.
Yes, I guess.
It'll be consistent with what we do with the server.

Of course, if you also have a solution how to reduce the number of
packages, that'd be perfect :)

Hmm, how about that?
We rename the following packages to remove "-10.1" at the end.


This way the server package will specify the version (either
"mariadb-server-10.1" for 10.1 or "mariadb-server" for the latest)
and everything else will follow.

Looks logical and doesn't increase the number of packages (!!!).
But I need to try whether it'll actually work in Debian :)

Wow ! Someone understood what I mean. Thank you a lot Sergei, I though I
was crazy seeing other people's answers
well, i don't get why there needs to be a metapackage at all


these are different repos and you have either 10.1 or 10.2 enabled

whatever packages in whatever versions are there, the update manager without mention a version explicit takes the one with the highest number independent of a new install or update

%package           server
Summary:           The MariaDB server and related files
Requires: %{name} = %{epoch}:%{version}-%{release}, %{name}-libs = %{epoch}:%{version}-%{release}
Requires:          sh-utils
Requires(pre):     shadow-utils
Provides: mysql-server = %{epoch}:%{version}-%{release}, mysql-server%{?_isa} = %{epoch}:%{version}-%{release}
Obsoletes:         mysql-server, community-mysql-server
%description       server

"dnf install mysql-server" == "dnf install mariadb-server" == "dnf install community-mysql-server"

why? because the Provides/Obsoletes in my spec say so