it was mentioned to give a user choice as to what to use. i have seen for instance when you install gnome aside kde it asks you what desktop manager you want to use. Wouldnt something like that be needed in this situation?<br>
<br><div class="gmail_quote">On Mon, Nov 8, 2010 at 9:18 PM, Kristian Nielsen <span dir="ltr"><<a href="mailto:knielsen@knielsen-hq.org">knielsen@knielsen-hq.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Lionel Elie Mamane <<a href="mailto:lionel@mamane.lu">lionel@mamane.lu</a>> writes:<br>
<br>
> On Tue, Feb 09, 2010 at 10:40:59PM +0100, Kristian Nielsen wrote:<br>
>> Some additional information that might be useful:<br>
><br>
>> - apt-able repositories of MariaDB are available from <a href="http://ourdelta.org/" target="_blank">http://ourdelta.org/</a><br>
><br>
>> - Package scripts for .deb are maintained on Launchpad: <a href="https://launchpad.net/ourdelta" target="_blank">https://launchpad.net/ourdelta</a><br>
><br>
>> I can provide further information on the packaging scripts on request.<br>
><br>
> I started to look into MariaDB; I was considering inclusion of MariaDB<br>
> in Debian proper, and to this effect was wondering:<br>
><br>
> 1) Does the ourdelta team judge the packaging mature enough for that<br>
> inclusion, or does it need more work?<br>
<br>
I think it is certainly mature enough. We have been building packages for 18<br>
month or so, and they are integrated in our daily build system with both<br>
builds and install+upgrade testing. And after all, they are based closely on<br>
the existing MySQL Debian packages, which are quite mature.<br>
<br>
The main issue that needs solving is to let MySQL and MariaDB packages<br>
co-exist in the same repository. Since MariaDB is essentially a different<br>
version of MySQL, we need a way for users to select which of the two<br>
alternatives they want. With current packaging, users choose by adding (or not<br>
adding) the MariaDB repository, and if they add it, MariaDB packages replace<br>
any corresponding MySQL packages.<br>
<br>
With the current packages in Debian, it is not possible to solve this<br>
satisfactorily (as far as I know). The problem is that there are other<br>
packages that have versioned "depends:" on MySQL packages, eg.<br>
libdbd-mysql-perl on libmysqlclient15off. So it is not possible for MariaDB to<br>
satisfy this dependency with a "provides:", even though MariaDB does include<br>
an alternative libmysqlclient.so.<br>
<br>
What has been discussed is to solve this by introducing virtual packages for<br>
libmysqlclient15off and similar packages; these would then depend: on<br>
mysql-xxx|mariadb-xxx packages. This requires changes to MySQL packages as<br>
well as to MariaDB packages.<br>
<br>
> 2) If a package for MariaDB based on the ourdelta packages gets<br>
> uploaded into Debian proper, how does the ourdelta team see<br>
> cooperation there?<br>
><br>
> Would ourdelta become the maintainers of the Debian package<br>
> (within Debian), or would you rather see it as a cooperation<br>
> between ourdelta and a separate (but possibly overlapping in<br>
> composisition) Debian team? In any of these cases, I'm considering<br>
> getting involved.<br>
<br>
I think either could work. We in MariaDB are mostly developers rather than<br>
packagers, so it might make sense to coorperate with a separate team. More<br>
Debian experience would only help integrate the packages better with the rest<br>
of Debian. But we are certainly willing to help out, including doing the work<br>
of developing and maintaining the packages should that be needed.<br>
<br>
> As far as uploading to Debian is concerned, the workflow could<br>
> look something like:<br>
><br>
> * Any team member can commit to the vcs repository, even if not<br>
> having Debian Developer status.<br>
><br>
> * Each upload to Debian has to be vetted by a Debian Developer<br>
> (from the team).<br>
<br>
It sounds reasonable, though I am not sufficiently familiar with Debian<br>
development to really understand the issue and possibilities.<br>
<br>
> 3) What is the Debian MySQL maintainers team take on this? Would it<br>
> in some way like to take care of MariaDB, too?<br>
<br>
If they are interested and have the time, it would certainly make sense that<br>
they are involved. MariaDB packaging is very close to MySQL packaging, and<br>
such involvement could help both to maintain consistency between the packaging<br>
of the two, as well as with the seamless integration with respect to user's<br>
choice between them.<br>
<br>
> It is naturally too late for inclusion in Squeeze (Debian 6.0), but<br>
> aiming for the release after that should be doable.<br>
<br>
Sounds good!<br>
<br>
- Kristian.<br>
<br>
_______________________________________________<br>
pkg-mysql-maint mailing list<br>
<a href="mailto:pkg-mysql-maint@lists.alioth.debian.org">pkg-mysql-maint@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/pkg-mysql-maint" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/pkg-mysql-maint</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Jonathan Aquilina<br>