Hi,

JFTR, I have no need for this feature any more, and nothing to comment here. Do 
as you think is best.

Joachim 

Am 30. Juni 2016 16:39:23 MESZ, schrieb Paul Gevers <elb...@debian.org>:
>Control: tags -1 moreinfo
>
>Hi Joachim,
>
>Sorry that it took so long to get back to this issue. I took over
>dbconfig-common a while ago and are now at the stage where I can
>comment
>on this request.
>
>On Thu, 21 Dec 2006 17:50:45 +0000 Joachim Breitner
><nome...@debian.org>
>wrote:
>> it would be nice if this scenario were supported:
>> 
>> Two package, one a frontend and one a real dbconfig package, should
>be
>> able to share the configuration by setting the same package name in
>the
>> calls to dbc_go.
>
>Close. What if you leave the package name as they really are, but
>provide the same dbname and dbuser in the config file of you
>(hypothetical) package?
>
>> Currently it seems to fail when the frontend package is purged,
>> confusing the other package.
>
>Yes, that is because the package name is the same, while that is not
>really true. It probably fails on the debconf templates being removed.
>
>> Note that I do not have that setup any more with my packages, so I
>don’t
>> have a developing test case. But it’s still a nice to have item :-)
>
>So I think this bug can be closed as already supported. Would be great
>if somebody could check this (maybe I need a example package in this
>area).
>
>Paul

Reply via email to