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."
Attachment:
signature.asc
Description: This is a digitally signed message part.