Hi, On Sun, Feb 13, 2011 at 05:07:57PM +0100, Sean Finney wrote: > yeah, currently i think the priorities are semi-hardcoded. The only > priorities that are variable are set based on whether or not the admin > has stated they want to show "remote" related questions (hostname, etc), > and whether or not it's a normal install vs. a 'frontend' install.
Right, exactly. > but i think it does make a lot of sense to make it a bit more variable, > so that you could raise the visibility of a specific question, etc. do > you have a hypothetical use case or two to illustrate what you'd like? Well basically I think that at the moment (and again as in #607171 this is for this Symfony2 packaging thing), for installation on remote hosts, we basically end up with a situation where you aren't asked enough questions to end up with a fully configured database, unless you set debian priority to low or medium. I haven't tested with local databases, and this problem could be caused by misuse. I see an option called dbc_remote_questions_default which seems to cause the priority to jump to high - does that mean I can just set that? If so, does it mean that if remote questions are not the default, but an option, we get into this state anyway? Sorry, this is really not a very concrete use-case. Thanks if you can distill what I've said into something meaningful :) Cheers P -- /* --------------------------------------------------- Penny Leach | http://mjollnir.org | http://she.geek.nz GPG: 8347 00FC B5BF 6CC0 0FC9 AB90 1875 120A A30E C22B --------------------------------------------------- */
signature.asc
Description: Digital signature
