| |||||||||||||
MariaDB: Disappearing test cases or did another part of MySQL just become closed source?MariaDB: Disappearing test cases or did another part of MySQL just become closed source?Posted Aug 19, 2012 1:50 UTC (Sun) by ewan (subscriber, #5533)In reply to: MariaDB: Disappearing test cases or did another part of MySQL just become closed source? by cmccabe Parent article: MariaDB: Disappearing test cases or did another part of MySQL just become closed source?
What there doesn't seem to be is a single preferred fork that everyone just moves to as there (more or less) was with LibreOffice, and for a non-Oracle example, X.org. Without that a lot of users stay with MySQL out of sheer momentum.
(Log in to post comments)
MariaDB: Disappearing test cases or did another part of MySQL just become closed source? Posted Aug 19, 2012 2:56 UTC (Sun) by drag (subscriber, #31333) [Link]
Most people will probably just stick with the version that is easiest to install.
Distros and repos Posted Aug 19, 2012 9:56 UTC (Sun) by man_ls (subscriber, #15091) [Link] Which most of the time means: most people stick with whatever their distro has. For instance, neither MariaDB or Percona are packaged in Debian so they are out for me.That is, if I ever wanted to leave the marvelous MongoDB and come back into the land of fixed schemas, which I don't. Ironically, for MongoDB I am ready to pay the price of adding a repo just to use a more recent version, 2.0 in this case. Having vendor-maintained and up-to-date repos is good. Note that MariaDB has no repo for Debian testing (wheezy), for example -- I use MongoDB on my dev machine with wheezy and it runs very well. First I would not use a database not in my distro, then I actually use a database on a separate repo. Why the contradiction? Actually there is no contradiction: I started using MongoDB from my distro, and only once I was sure it was worth it I upgraded to the distro-supplied version. But having it available inside Debian was a big plus.
Coming back to your comment, both were really, really easy to install. A separate repo makes it harder to replicate the configuration on a new machine, but only by a small amount: add a file to
Distros and repos Posted Aug 20, 2012 7:24 UTC (Mon) by drag (subscriber, #31333) [Link]
Personally, I wouldn't hesitate to use a database if it's a supported configuration by the vendor (aka 'upstream') with binaries they provide. Adding a repo (or equivelent) isn't a big deal because I am going to have to have some way to manage configurations anyways.
It's more important to me for upstream support then distro support... but whether or not I choose to do that depends on the circumstances.
Usually I am not concerned with the database so much because when I, and most people use databases, it is generally because we have a app or framework we want to run that depends on them. The configuration and everything is going to be managed by the application install scripts and deviating from their documentation just means irritation and time spent on something that isn't really going to matter.
If the MariaDB folks want to have people use their software then the biggest first step is going to get the distros to swap in their software in replace of Oracle's. This sort of thing happens fairly frequently with software in distribution repo's.
:)
Distros and repos Posted Aug 21, 2012 8:53 UTC (Tue) by mariuz (guest, #24892) [Link]
you can install quite easily Firebird in debian sid/testing/stable and ubuntu
|
|||||||||||||