hi sean,
On Tue, Jun 13, 2006 at 09:22:34AM -0400, sean finney wrote:
> On Tue, Jun 13, 2006 at 02:49:29PM +0200, Michael Ablassmeier wrote:
> > yes, that'd be great. Something like having 2 profiles for
> > dbconfig-common, one that does actually do the whole database
> > modification stuff and another one which can be used to ask a certain
> > set of questions, only for creating a include file (which could be used
> > for client-only packages)..
>
> i imagine the way this would work would be something like setting the
> following variables before calling dbc_go in the config hook:
>
> dbc_client_package="true"
> dbc_reference_package="foopackage"
> dbc_go ...
>
> and then the dbc hooks would ask the questions (perhaps slightly
> differently to clarify that they won't be setting up the database).
> it can also look for the dbc config file for foopackage (in the case
> that they are installed on the same host) and preseed it with default
> answers to these questions.
>
> an alternate path would be to provide a new set of maintainer hooks
> /usr/share/dbconfig-common/dpkg/postinst.mysql.client etc, which would
> effecitvely do the same thing behind the scenes and not require any
> extra configuration/variables to be set. i'll have to do a bit more
> testing/hacking before i can comment on which way i want to run with this.
i would prefer an alternate path for a new set of maintainer hooks as
proposed. However, i leave that up to you, thanks again for your work!
bye,
- michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
