Bug#513382: bug against mysql package for a non-autostarting mysqld
It has been stated several times in this bug that the mysql maintainers have been approached about providing a package containing mysqld that does not auto-start a global mysqld instance. However I can find no such bug in the BTS filed against src:mysql-dfsg-5.1, archived or otherwise. If such a big exists then this one should be set to be blocked by the other; otherwise, such a bug should have been filed ages ago. -- Jon Dowland signature.asc Description: Digital signature
Bug#513382: bug against mysql package for a non-autostarting mysqld
On Saturday 17 October 2009 14:16:21 Jon Dowland wrote: It has been stated several times in this bug that the mysql maintainers have been approached about providing a package containing mysqld that does not auto-start a global mysqld instance. Yup. I have discussed it quite some time ago with Norbert (nobse) and he said that he welcomed patches but didn't have time to do it himself. I unfortunately haven't had time either. Ubuntu has done the split, so if someone is having time on their hands, trying to figure out if it is usable for debian and how it is usable would be a good thing. It is somewhere on my todolist, but it is unfortunately neverending. However I can find no such bug in the BTS filed against src:mysql-dfsg-5.1, archived or otherwise. If such a big exists then this one should be set to be blocked by the other; otherwise, such a bug should have been filed ages ago. A bug exists. I currently can't find it, but I know it does. Note that mysql have switched source package names a couple of times. /Sune -- How to close the e-mail address? The point is that from DOS you either must overclock a controller, or can never explore a monitor on the serial 3D cache of the provider to the hardware for unmounting a BIOS on the MIDI DVD tool. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513382: bug against mysql package for a non-autostarting mysqld
Hello, On šeštadienis 17 Spalis 2009 18:03:09 Ritesh Raj Sarraf wrote: Jon Dowland wrote: It has been stated several times in this bug that the mysql maintainers have been approached about providing a package containing mysqld that does not auto-start a global mysqld instance. Won't just disabling mysql init script suffice ? Why roll out a full blown package for that ? You gotta be kidding, aren't you? Why would all Debian KDE users care how to disable a mysql init script (which there is no decent user-friendly way anyway) which they do not care about and which is supposed to be handled transparently. Not an option. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#513382: bug against mysql package for a non-autostarting mysqld
On Saturday 17 Oct 2009 21:23:05 Modestas Vainius wrote: Hello, On šeštadienis 17 Spalis 2009 18:03:09 Ritesh Raj Sarraf wrote: Jon Dowland wrote: It has been stated several times in this bug that the mysql maintainers have been approached about providing a package containing mysqld that does not auto-start a global mysqld instance. Won't just disabling mysql init script suffice ? Why roll out a full blown package for that ? You gotta be kidding, aren't you? Why would all Debian KDE users care how to disable a mysql init script (which there is no decent user-friendly way anyway) which they do not care about and which is supposed to be handled transparently. Not an option. No really. Shipping the same binary twice is not the best thing to do either. I agree that not every one would know how to disable an init script. How about leaving the mysqld binary package as it is. Just provide a basic mysql-akonadi package that creates a /etc/default/mysql-akonadi file with mysqld system instance set to off. (The msyqld package could just be changed to check for this file and source it, if available). akonadi can then depend on just mysql-akonadi. And if there are users (like me) who don't want to have one mysql for akonadi and another one for amarok, can still go ahead and set mysql system instance to 'on' in /etc/default/mysql-akonadi. Should cover all and still not require to ship the mysqld. Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: This is a digitally signed message part.
Bug#513382: bug against mysql package for a non-autostarting mysqld
Sveiki, On šeštadienis 17 Spalis 2009 19:10:45 Ritesh Raj Sarraf wrote: You gotta be kidding, aren't you? Why would all Debian KDE users care how to disable a mysql init script (which there is no decent user-friendly way anyway) which they do not care about and which is supposed to be handled transparently. Not an option. No really. Shipping the same binary twice is not the best thing to do either. I agree that not every one would know how to disable an init script. Ubuntu solution: mysql-server-core-5.1 ships mysqld, no init stuff. mysql-server-5.1 ships init stuff. How about leaving the mysqld binary package as it is. Just provide a basic mysql-akonadi package that creates a /etc/default/mysql-akonadi file with mysqld system instance set to off. (The msyqld package could just be changed to check for this file and source it, if available). akonadi can then depend on just mysql-akonadi. And if there are users (like me) who don't want to have one mysql for akonadi and another one for amarok, can still go ahead and set mysql system instance to 'on' in /etc/default/mysql-akonadi. Should cover all and still not require to ship the mysqld. Way too overcomplicated solution for a rather simple problem. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
