On Sat, Oct 09, 2004 at 08:02:22AM +0200, Andreas Tille wrote:
> On Fri, 8 Oct 2004, Stefan Hornburg wrote:
>
> >First of all documentation.
> Definitely!
I was about to write some, to at least have an overview of what commands
are available. Unfortunately, I haven't found the time yet.
Uwe
--
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
> > should depend u
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
> make up, translator
On Fri, 8 Oct 2004, Stefan Hornburg wrote:
First of all documentation.
Definitely!
Kind regards (and sorry for the ACK message - but it was so necessary)
Andreas
On Fri, 8 Oct 2004 15:26:41 +0200
[EMAIL PROTECTED] (Uwe Steinmann) wrote:
> On Fri, Oct 08, 2004 at 03:45:26PM +1000, Andrew Pollock wrote:
> > On Thu, Oct 07, 2004 at 05:19:07PM +0200, Uwe Steinmann wrote:
> > > On Thu, Oct 07, 2004 at 03:38:59PM +0200, Philipp Matthias Hahn wrote:
> > > > Hello
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
On Thu, 2004-10-07 at 23:36, sean finney wrote:
> On Thu, Oct 07, 2004 at 03:38:59PM +0200, Philipp Matthias Hahn wrote:
> > What is consideres best practice when a package uses a SQL database
> > (mysql, postgresql) and needs to create its own catalog and/or tables?
I am the postgresql maintainer
On Thu, Oct 07, 2004 at 06:36:27PM -0400, sean finney wrote:
> - don't store the pw in debconf, or at least ask the admin first
That's no problem. Debconf is, by default, configured correctly to not
store passwords /anywhere/ -- at least not if you use a password type of
template, which you should
On 07-Oct-04, 10:19 (CDT), Uwe Steinmann <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 07, 2004 at 03:38:59PM +0200, Philipp Matthias Hahn wrote:
> > Hello!
> >
> > What is consideres best practice when a package uses a SQL database
> > (mysql, postgresql) and needs to create its own catalog and/or ta
On Fri, Oct 08, 2004 at 03:45:26PM +1000, Andrew Pollock wrote:
> On Thu, Oct 07, 2004 at 05:19:07PM +0200, Uwe Steinmann wrote:
> > On Thu, Oct 07, 2004 at 03:38:59PM +0200, Philipp Matthias Hahn wrote:
> > > Hello!
> > >
> > > What is consideres best practice when a package uses a SQL database
>
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 wheeland
> make
On Thu, 7 Oct 2004, Peter Eisentraut wrote:
I say, create the tables when the package starts for the first time. As
an analogy, programs using Berkeley-type databases normally set up
their databases automatically when they run and don't require postinst
processing.
Hmmm, I doubt I understand this
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 set of debconf
> >templates
> 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 interacting with RDBMS
establish a set of *common* debconf templates for prompting users ?
While t
On Thu, Oct 07, 2004 at 05:19:07PM +0200, Uwe Steinmann wrote:
> On Thu, Oct 07, 2004 at 03:38:59PM +0200, Philipp Matthias Hahn wrote:
> > Hello!
> >
> > What is consideres best practice when a package uses a SQL database
> > (mysql, postgresql) and needs to create its own catalog and/or tables?
hi phillip,
On Thu, Oct 07, 2004 at 03:38:59PM +0200, Philipp Matthias Hahn wrote:
> What is consideres best practice when a package uses a SQL database
> (mysql, postgresql) and needs to create its own catalog and/or tables?
this is a very good question, which has not been conclusively answered
On Thu, Oct 07, 2004 at 03:38:59PM +0200, Philipp Matthias Hahn wrote:
> Hello!
>
> What is consideres best practice when a package uses a SQL database
> (mysql, postgresql) and needs to create its own catalog and/or tables?
>
> [ ] Disable the package until someone has manually setup the databas
Philipp Matthias Hahn wrote:
> What is consideres best practice when a package uses a SQL database
> (mysql, postgresql) and needs to create its own catalog and/or
> tables?
I say, create the tables when the package starts for the first time. As
an analogy, programs using Berkeley-type databases
Hello!
What is consideres best practice when a package uses a SQL database
(mysql, postgresql) and needs to create its own catalog and/or tables?
[ ] Disable the package until someone has manually setup the database?
[ ] Ask a lot of questions via debconf and try to setup in postconf?
I ask beca
21 matches
Mail list logo
