On 11/18/2010 07:06 PM, BJ Dierkes wrote: > > Hello all, > > This is more for Monty and I, but figured I'd bring it on list. Reference > the following: > > https://bugs.launchpad.net/drizzle/+bug/669744 > > > I wanted to bring up the fact that per Fedora packaging policies, hard > 'conflicts' are to be avoided as much as possible. For that reason I am > opting to not add the hard 'Conflicts' on the drizzle7-mysql-protocol > subpackage (Conflicts: mysql-server). Instead I am disabling the > configuration by default, making the resolution of the inherent conflict up > to the user to resolve. Meaning, should you need to.. you could have > mysql-server and drizzle7-mysql-protocol functioning simultaneously, with > non-conflicting configurations (i.e. running mysql_protocol on something > other than 3306). > > The drizzle7-mysql-protocol subpackage will not load the plugin by default, > but will provide the following configuration: > > [wdier...@fc14 ~]$ cat /etc/drizzle/conf.d/mysql_protocol.cnf > # MySQL Protocol Configuration > # --- > # This configuration is disabled by default, as it potentially conflicts > # with mysqld. Uncomment the settings below to enable the mysql_protocol > # plugin. > # --- > > # plugin-add = mysql_protocol > # mysql-protocol.port = 3306 > > > So, if the user wants to enable the protocol then they need to modify the > configuration. Otherwise, the package would inherently conflict with > mysql-server if mysqld were running on the default port 3306. > > Any thoughts?
As a follow up to this, in the debian package drizzle-plugin-mysql-protocol _does_ conflict with mysql-server and _does_ enable the mysql-protocol port on 3306 if you install it. In fact, all of the plugin packages enable their respective plugins. _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
