> Should this be in the wrapper, or in the one-time migration code in
> mysql-common when my.cnf.migrated is generated? I'm happy with the
> latter, especially as you point out a regular conffile prompt would
> happen anyway. I'm concerned about "too many debconf prompts" for the
> former.
>
> We could additionally provide the notice on mysql-common.postinst every
> time that my.cnf.migrated is present and active, perhaps filtered by
> version. This might help users who have upgraded already.
Either or both are OK to me, choose whatever you think is simpler to
implement or makes more sense.
The helper text prepended to the migrated my.cnf could also be
improved a bit. It does not tell the user _why_ the
update-alternatives is used and what the alternatives are.
Unfortunately I can't come up with a smart and short text to put there
from the top of my head.
@maier-m: Do you feel you could contribute to improve the documentation part?
> Should this be in the wrapper, or in the one-time migration code in postinst every
> mysql-common when my.cnf.migrated is generated? I'm happy with the
> latter, especially as you point out a regular conffile prompt would
> happen anyway. I'm concerned about "too many debconf prompts" for the
> former.
>
> We could additionally provide the notice on mysql-common.
> time that my.cnf.migrated is present and active, perhaps filtered by
> version. This might help users who have upgraded already.
Either or both are OK to me, choose whatever you think is simpler to
implement or makes more sense.
The helper text prepended to the migrated my.cnf could also be
improved a bit. It does not tell the user _why_ the
update-alternatives is used and what the alternatives are.
Unfortunately I can't come up with a smart and short text to put there
from the top of my head.
@maier-m: Do you feel you could contribute to improve the documentation part?