[opensuse] MySQL Plugins - Public Opinion
Hi all, maybe some of you already knows. There is a new stable release of MySQL - version 5.1.30. What's new? Among other things, one new feature is a possibility to compile some of the backends as plugins. From this option some questions arise how to prepare this package. In the rest of this mail I want to propose several possibilities how to package new MySQL and I want to ask what is the best choice according to the public opinion of our community. I'm not promising that the option with most votes will be chosen, but your votes will certainly affects final decision somehow. What backends can be compiled as modules? - archive - federated - innodb - blackhole - example What are the possibilities? Packaging possibilities: 1) Make it as much modular as it is possible. Everything what can be build as a module will be build as a module and let the people choose what they really want. 1a) Some modules are even developed separately so in the future maybe we can even have newer modules then the version shipped with MySQL 2) Compile most popular backends as an internal part of MySQL and let only some not so popular as plugins. If you are voting for this option please state which backend is your favorite (you can state more then one of course) 3) Compile everything as an internal part of MySQL. Installation possibilities: (i) All plugins are disabled by default (ii) All plugins are enabled by default if you are installing new MySQL, disabled after upgrade from 5.0, keep untouched if upgrading from 5.1 (iii) All plugins are enabled by default if you are installing new MySQL, enabled after upgrade from 5.0, keep untouched if upgrading from 5.1 Nearly every choice has some advantages and disadvantages. With modular MySQL you can enable only things you really need and disable those you don't. It may even provide more frequent updates (choice 1a). On the other hand, statically linked version of backends was used till now and it's widely tested scenario... Enabling plugins by default has advantages for new users as they wouldn't need to know how to enable them. On the other hand it can confuse advanced users, although they can disable them and most likely they will know how to do that. So if you just want to vote, you can send me private e-mail with your choice so we don't flood mailing list with voting. On the other hand if you've got something important to say what may influence the opinion of the others you can vote in public and state you opinion. Or if question needs some additional clarification feel free to ask it. I'll collect votes from both sources. If you want to try new version, testing version can be obtained from buildservice, project server:database:mysql51. Current configuration should be combination of options 1+(iii). Last note, it's probably not a good idea to test this on production server yet. Repository URL: http://download.opensuse.org/repositories/server:/database:/mysql51/openSUSE... http://download.opensuse.org/repositories/server:/database:/mysql51/openSUSE... http://download.opensuse.org/repositories/server:/database:/mysql51/openSUSE... http://download.opensuse.org/repositories/server:/database:/mysql51/openSUSE... -- Michal Hrusecky Package Maintainer SUSE LINUX, s.r.o e-mail: mhrusecky@suse.cz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 21 January 2009, Michal Hrusecky <mhrusecky@suse.cz> wrote about '[opensuse] MySQL Plugins - Public Opinion':
Packaging possibilities:
1) Make it as much modular as it is possible. Everything what can be build as a module will be build as a module and let the people choose what they really want.
I vote here. Specifically, introduce mysql-core and a mysql-$plugin for each plugin. Have the mysql package bring in -core and all -${plugin}s that are currently in 5.0. Have mysql-full bring in -core and all -${plugin}s that are packaged, as long as no -$plugin conflicts with a different one. Eventually, transition to the mysql package bringing in -core and popular/expected plugins -- basically tuned toward "the average user" instead of "exactly what 5.0 users expect".
(iii) All plugins are enabled by default if you are installing new MySQL, enabled after upgrade from 5.0, keep untouched if upgrading from 5.1
I vote here. Installing the plugin should be enough to enable it, and if people want to disable plugins they have installed they can do it manually. If a plugin has a history of security issues, then possibly change the default for that specific plugin to disabled. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Boyd Stephen Smith Jr. - 13:45 21.01.09 wrote:
On Wednesday 21 January 2009, Michal Hrusecky <mhrusecky@suse.cz> wrote about '[opensuse] MySQL Plugins - Public Opinion':
Packaging possibilities:
1) Make it as much modular as it is possible. Everything what can be build as a module will be build as a module and let the people choose what they really want.
I vote here. Specifically, introduce mysql-core and a mysql-$plugin for each plugin. Have the mysql package bring in -core and all -${plugin}s that are currently in 5.0. Have mysql-full bring in -core and all -${plugin}s that are packaged, as long as no -$plugin conflicts with a different one. Eventually, transition to the mysql package bringing in -core and popular/expected plugins -- basically tuned toward "the average user" instead of "exactly what 5.0 users expect".
Thank you for voting. If I understand correctly you are suggesting that mysql package will be virtual package which will install mysql-core which will be bare MySQL without any plugins and all usual myslq-*-plugin packages... This is certainly interesting idea. -- Michal Hrusecky Package Maintainer SUSE LINUX, s.r.o e-mail: mhrusecky@suse.cz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 2009 January 22 03:10:14 Michal Hrusecky wrote:
Boyd Stephen Smith Jr. - 13:45 21.01.09 wrote:
On Wednesday 21 January 2009, Michal Hrusecky <mhrusecky@suse.cz> wrote
about '[opensuse] MySQL Plugins - Public Opinion':
Packaging possibilities:
1) Make it as much modular as it is possible. Everything what can be build as a module will be build as a module and let the people choose what they really want.
I vote here. Specifically, introduce mysql-core and a mysql-$plugin for each plugin. Have the mysql package bring in -core and all -${plugin}s that are currently in 5.0. Have mysql-full bring in -core and all -${plugin}s that are packaged, as long as no -$plugin conflicts with a different one. Eventually, transition to the mysql package bringing in -core and popular/expected plugins -- basically tuned toward "the average user" instead of "exactly what 5.0 users expect".
Thank you for voting. If I understand correctly you are suggesting that mysql package will be virtual package which will install mysql-core which will be bare MySQL without any plugins and all usual myslq-*-plugin packages... This is certainly interesting idea.
I'm not sure about the terminology, being most familiar with Debian packaging. "Over there", a virtual package is a package name that is Provided by one or more real packages that does not actually exist, and that's not what I'm suggesting. "Over there", a meta-package is empty or nearly empty package that mainly exists to pull in other packages through its Depends, Recommends, and Suggests. I am suggesting a mysql-5.1 meta-package to ease the transition for people using the mysql-5.0 (real) package, while also moving forwards with modular (real) packages: mysql-core-5.1 and mysql-${plugin_api}-foo-plugin-${plugin_version}. I hope that was clearer. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Boyd Stephen Smith Jr. - 10:57 22.01.09 wrote:
I'm not sure about the terminology, being most familiar with Debian packaging. "Over there", a virtual package is a package name that is Provided by one or more real packages that does not actually exist, and that's not what I'm suggesting. "Over there", a meta-package is empty or nearly empty package that mainly exists to pull in other packages through its Depends, Recommends, and Suggests. I am suggesting a mysql-5.1 meta-package to ease the transition for people using the mysql-5.0 (real) package, while also moving forwards with modular (real) packages: mysql-core-5.1 and mysql-${plugin_api}-foo-plugin-${plugin_version}.
I hope that was clearer.
Yes, that's exactly how I understood it. Well, currently I'm using mysql package for core application and it recommends plugins. But with metapackage it may be more obvious that something changed. Well, I'll do some more testing with updating and new installation to make sure that users wouldn't get confused. Thank you again for sharing your opinion. -- Michal Hrusecky Package Maintainer SUSE LINUX, s.r.o e-mail: mhrusecky@suse.cz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Boyd Stephen Smith Jr. wrote:
On Wednesday 21 January 2009, Michal Hrusecky <mhrusecky@suse.cz> wrote about '[opensuse] MySQL Plugins - Public Opinion':
Packaging possibilities:
1) Make it as much modular as it is possible. Everything what can be build as a module will be build as a module and let the people choose what they really want.
I vote here. Specifically, introduce mysql-core and a mysql-$plugin for each plugin. Have the mysql package bring in -core and all -${plugin}s that are currently in 5.0. Have mysql-full bring in -core and all -${plugin}s that are packaged, as long as no -$plugin conflicts with a different one. Eventually, transition to the mysql package bringing in -core and popular/expected plugins -- basically tuned toward "the average user" instead of "exactly what 5.0 users expect".
(iii) All plugins are enabled by default if you are installing new MySQL, enabled after upgrade from 5.0, keep untouched if upgrading from 5.1
I vote here. Installing the plugin should be enough to enable it, and if people want to disable plugins they have installed they can do it manually. If a plugin has a history of security issues, then possibly change the default for that specific plugin to disabled.
+1 - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkl4OZ8ACgkQasN0sSnLmgJnMQCeOoSYARwEmeX132+2D8qDu8HD il0AoK9At9Ukh494tk6jj2p0bYjsdmVA =6yQf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Boyd Stephen Smith Jr. -
G T Smith -
Michal Hrusecky