[debian-mysql] Groping for a roadmap in the dark

[Olaf van der Spek]

On Fri, Jun 8, 2012 at 1:55 PM, Nicholas Bamber <nicholas at periapt.co.uk> wrote:
>> Piuparts is an awesome assessment of where we stand w.r.t. policy. Its
>> true,
>> we are not automatically purging data if the question about whether or not
>> to remove /var/lib/mysql/* is left to defaults.
>>
>> I'd entertain making mysql-server-5.5/postrm_remove_databases default to
>> true
>> rather than false, as long as it is noted in NEWS, and the question is
>> given
>> a high priority. As I understand it, this would solve the issue entirely.
>
>
> It seems we are in agreement. Basically I think we need to do everything we
> can to alert the user to this change. This will include having the change in
> either experimental or unstable for most of wheezy+1.
>
> Olaf however will doubtless disagree. I would like to make sure he has an
> opportunity to make his case. There is a while before I get  to piuparts on
> the roadmap.

Certainly. Do we know what Postgres does yet? Do we know if a piuparts
exception is possible?

Users don't (like to) read docs. They might not read NEWS, for
whatever reason. Users shouldn't be bothered.
AFAIK purge doesn't delete data, it deletes conf. Users expect the
same, otherwise you wouldn't have to bother with NEWS and questions.

It's like first setting a trap and then putting up a warning sign.

Why are we trying so hard to avoid a piuparts exception?


> So I throw the question back to you. How would you respond to #511438?

How big is the test and other optional stuff? If it's significant it
seems reasonable to split it.

>>> 6.) Config modularity. The modern way would
>>> be for mysql-config to store a skeleton /etc/mysql/my.cnf and something
>>> to keep
>>> /etc/mysql/conf.d alive. However we will have to keep just enough
>>> in /etc/mysql/my.cnf not to break the existing 5.5. Each of the packages
>>> would own its appropriate config fragment below /etc/mysql/conf.d .

Maybe we should remove documentation (and commented entries) from conf
files. It's easy to include a link to the documentation and a clean
conf file is easier to read.

Greetings,

Olaf