On Thu, Oct 14, 2004 at 03:44:00PM -0400, Joey Hess wrote:
> Brian Sutherland wrote:
> > Am I missing something?
>
> Only that dpkg-preconfigure is not guaranteed to be called,
Thanks for pointing out this, Joey
> and if it is
> called, there is nothing really to ensure that it runs for all deb
Brian Sutherland wrote:
> Ah yes, thanks. A little bit of testing confirms for me that merely
> having a depends on a package (ssl-cert) is enough to be able to
> register and ask questions from that package. Even on first install
> on a clean chroot.
>
> So, it dosn't seem necessary to do any c
On Thu, Oct 14, 2004 at 03:16:27PM +0200, Agustin Martin wrote:
> On Thu, Oct 14, 2004 at 02:30:32AM -0400, sean finney wrote:
> I might be wrong, but I do not think so, if things were this way, debconf
> shared questions as described in the debconf manual would never work at the
> .config stage, b
On Thu, Oct 14, 2004 at 02:30:32AM -0400, sean finney wrote:
>
> yes, it'd have to be rebuilt with the new templates every time they were
> updated, which is definitely a shortcoming.
We did some sort of this in the ancient experimental dictionaries-common
policy, before it was even made semi-o
On Wed, Oct 13, 2004 at 03:09:14PM -0400, Joey Hess wrote:
> Brian Sutherland wrote:
> > What about a rule that says:
> >
> > - If the package name is the same as the directory in the debconf database
> > then use that package's templates take priority.
> > - Else, as before.
>
> Suppose that:
On Wed, Oct 13, 2004 at 11:16:09PM +0200, Agustin Martin wrote:
> But for shared/* debconf templates this means that all packages using that
> template need to be rebuilt against the new template-providing package
> after every change in its template contents. I think that is better to
> split the
Brian Sutherland wrote:
> What about a rule that says:
>
> - If the package name is the same as the directory in the debconf database
> then use that package's templates take priority.
> - Else, as before.
Suppose that:
1. package A is preconfigured, and has an A/template
2. package B is preco
On Wed, Oct 13, 2004 at 08:38:58AM -0400, sean finney wrote:
> if the templates are included at build-time by a debhelper-style script,
> there's no need for a runtime dependency for these templates.
>
But for shared/* debconf templates this means that all packages using that
template need to be
On Wed, Oct 13, 2004 at 08:38:58AM -0400, sean finney wrote:
> On Wed, Oct 13, 2004 at 11:51:00AM +0200, Brian Sutherland wrote:
> > The package includes the template-package's templates at build
> > (debhelper style as suggested before).
> >
> > Then up to date translations can be ensured by inst
On Wed, Oct 13, 2004 at 11:51:00AM +0200, Brian Sutherland wrote:
> The package includes the template-package's templates at build
> (debhelper style as suggested before).
>
> Then up to date translations can be ensured by installing a
> debconf-translation-templates meta package or templates pack
On Tue, Oct 12, 2004 at 10:05:40PM +0200, Agustin Martin wrote:
> On Mon, Oct 11, 2004 at 12:59:01PM +0200, Brian Sutherland wrote:
> > On Mon, Oct 11, 2004 at 07:36:40AM +0200, Christian Perrier wrote:
> > > SHARED TEMPLATES
> > >It's actually possible to have a template and a question tha
On Mon, Oct 11, 2004 at 12:59:01PM +0200, Brian Sutherland wrote:
> On Mon, Oct 11, 2004 at 07:36:40AM +0200, Christian Perrier wrote:
> > SHARED TEMPLATES
> >It's actually possible to have a template and a question that
> >are shared among a set of packages. All the packages have t
> > SHARED TEMPLATES
> >It's actually possible to have a template and a question that
> >are shared among a set of packages. All the packages have to
> >provide an identical copy of the template in their templates
> ^
> >files. This can be
On Mon, Oct 11, 2004 at 07:36:40AM +0200, Christian Perrier wrote:
> SHARED TEMPLATES
>It's actually possible to have a template and a question that
>are shared among a set of packages. All the packages have to
>provide an identical copy of the template in their templates
Quoting Marc Haber ([EMAIL PROTECTED]):
> Do we have infrastructure to handle different answers for the same
> question? Maybe I'd like to have a different dbadmin password on my
> postgresql database than on mysql?
Yes, we have it through the REGISTER command in the debconf protocol
(see man de
Marc Haber wrote:
> Do we have infrastructure to handle different answers for the same
> question? Maybe I'd like to have a different dbadmin password on my
> postgresql database than on mysql?
This discussion is about having a common set of chunks of text available
somewhere for use in the debco
On Sun, Oct 10, 2004 at 03:18:52PM +0200, Marc Haber wrote:
> On Fri, 8 Oct 2004 06:59:50 +0200, Christian Perrier
> <[EMAIL PROTECTED]> wrote:
> >Could *please* maintainers of packages interacting with RDBMS
> >establish a set of *common* debconf templates for prompting users ?
> >
> >-Database us
On Fri, 8 Oct 2004 06:59:50 +0200, Christian Perrier
<[EMAIL PROTECTED]> wrote:
>Could *please* maintainers of packages interacting with RDBMS
>establish a set of *common* debconf templates for prompting users ?
>
>-Database user
>-Password for this user
>-Database administrator username
>-Database
On Fri, Oct 08, 2004 at 09:03:22AM +0200, Christian Perrier wrote:
> Indeed, this is a long time since I think about such "common debconf
> templates" package.
> The current way of handling common templates by the use of shared/* is
> not optimal ATM, as all packages using shared/* templates mus
On Sat, Oct 09, 2004 at 01:45:50PM +0200, Brian Sutherland wrote:
> On Fri, Oct 08, 2004 at 06:59:50AM +0200, Christian Perrier wrote:
> > All such templates should probably go into a common set of debconf
> > templates, provided by a very small package, which all these packages
&g
On Fri, Oct 08, 2004 at 06:59:50AM +0200, Christian Perrier wrote:
> All such templates should probably go into a common set of debconf
> templates, provided by a very small package, which all these packages
> should depend upon, instead of constantly reinvent the wheeland
On Fri, 8 Oct 2004 06:59:50 +0200
Christian Perrier <[EMAIL PROTECTED]> wrote:
> > if you think that it would be too complicated/flaky, i'd add a debconf
> > note (of _low_ priority!) and put something in README.Debian.
>
>
> While we are at it :
>
> Could *please* maintainers of packages inter
hi christian,
On Fri, Oct 08, 2004 at 06:59:50AM +0200, Christian Perrier wrote:
> All such templates should probably go into a common set of debconf
> templates, provided by a very small package, which all these packages
> should depend upon, instead of constantly reinvent the whe
On Fri, 8 Oct 2004, Christian Perrier wrote:
The only problem is that I'm damn unable to find a 25th hour in the
day for working on this.
Once I've read a childresn book where a damn bad guy had stolen the
Wednesday. The good boy in this book reconstructed the day the following
way:
- the "hou
(crossposted to -devel and -i18n...feel free to followup on the
appropriate place...it probably belongs to both currently)
Quoting Andreas Tille ([EMAIL PROTECTED]):
> On Fri, 8 Oct 2004, Christian Perrier wrote:
>
> >All such templates should probably go into a common se
*owner*).
All such templates should probably go into a common set of debconf
templates, provided by a very small package, which all these packages
should depend upon, instead of constantly reinvent the wheeland
make up, translators, do damn boring work.
Such "common debcon templat
26 matches
Mail list logo
