sean finney wrote:
hi olaf,
On Sun, May 14, 2006 at 07:26:54PM +0200, Olaf van der Spek wrote:
1 - nothing, stay with the status quo
2 - set a random password
3 - set an admin defined password
my order of preference is { 3 , 1 , 2 }. for reasons i think are
outlined in the bug's history.
I can't find the reasons that are still left. Could you please briefly
repeat the reasons for preferring 3 over 1 and 1 over 2?
sure:
2:
i don't like the idea of setting a random password arbitrarily because
it could lead to confusion, especially for existing installations.
Only doing it for new installations is enough IMO.
If a notification is send via debconf/email, it'd only lead to confusion
if the administrator doesn't read his email.
furthermore, i don't like the idea of putting a mysql adm password in a
file or otherwise communicating it to the admin on general principle.
It's a bit hard to argue against 'general principle'.
1:
i'm kind of ambivalent towards the current situation. or, i don't like
it, but i'm not that unhappy.
It'd indeed not a release critical issue. :)
3:
i like the idea of prompting the admin for a password, but only in a way
that won't be be annoying. that is, it shouldn't ask the admin if
the password is already set, and it shouldn't ask the admin every time.
Sounds reasonable, but isn't possible depending on debconf priority level.
It also introduces additional questions which is not an advantage on
general principle, especially if it can be avoided. :)
What if the question doesn't get asked?
If you choose to go with 3, I'd prefer a fallback to 2, not to 1.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
