[debian-mysql] Discussion on handling 5.6 related matters

Akhil Mohan akhil.mohan at oracle.com
Wed Jul 9 19:29:24 UTC 2014


Hi Robie,

Consider the case when a user goes for co-installed data dir for
multiple variants as /var/lib/fork{1,2,3,...} and plans to remove all
forks. I have following questions:

 1. Will purging the server package for each fork trigger removal of
    data dir or purging mysql-defaults will remove data dir ?
 2. If the removal is associated with mysql-defaults, then in
    co-installed setup will mysql-defaults remove all data dirs at once
    or allow selection ?
 3. If all data dirs will be removed together, then it is possible to
    accidentally remove more than required. How will we control this ?
 4. Since user might do manual data dir creation and also add the
    required entries in config manually so the mysql-defaults package
    may always not know if data dir is present and might remove user
    accounts owning the custom data dir leaving data inaccessible. Will
    we check for only standard data dirs or read them from config files ?
 5. I see possibility of config files getting custom location during
    manual setup ? Do we see this as trouble ?

Regards,
Akhil

On Wednesday 09 July 2014 06:53 PM, Robie Basak wrote:
> On Wed, Jul 09, 2014 at 02:52:03PM +0300, Otto Kekäläinen wrote:
>> I don't think we need co-installability, as admins are likely to pick
>> just on variant and then run it..?
> There are bugs filed in Launchpad that seem to have been triggered
> because users are trying to switch between variants, and /var/lib/mysql
> has confused matters. This is what I'd like to fix properly.
>
> I suppose co-installability isn't preciely what I'm looking for, but
> co-installability capability will mean that what I'm looking for is met.
>
> Exactly what I think I want is the ability for users to be able to
> switch between variants at will without anything screwing up. So, for
> example, the ability to switch from MySQL to MariaDB, and then switch
> back to MySQL for whatever reason later.
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20140710/f9a7f5aa/attachment.html>


More information about the pkg-mysql-maint mailing list