Re: debconf and program generated config

2005-04-05 Thread Michelle Konzack
Am 2005-04-04 21:41:46, schrieb Justin Pryzby: > > > > | tddyndns >/dev/null 2>&1 > Okay, as long as it fails if it should fail. You might only redirect > stderr or only stdout as necessary, to allow for better diagnostics. > Or maybe |grep -v 'message you don't want'. > > Or even |grep '.' &&

Re: debconf and program generated config

2005-04-04 Thread Justin Pryzby
On Tue, Apr 05, 2005 at 02:57:32AM +0200, Michelle Konzack wrote: > Hi, > > Am 2005-04-04 20:08:45, schrieb Justin Pryzby: > > > templates: defines the interactive prompts > > config: this is a shell script which asks the questions defined by > > templates. It handles things like "if you

Re: debconf and program generated config

2005-04-04 Thread Michelle Konzack
Hi, Am 2005-04-04 20:08:45, schrieb Justin Pryzby: > templates: defines the interactive prompts > config: this is a shell script which asks the questions defined by > templates. It handles things like "if you answer yes to X, then > ask Y, but not if you answer no". It exists such t

Re: debconf and program generated config

2005-04-04 Thread Justin Pryzby
On Tue, Apr 05, 2005 at 01:29:50AM +0200, Michelle Konzack wrote: > Hello, > > This is the first experience using debconf to configure a bunch of > options in a program. > > The program I am packing generate a config at its first start. Then the > admin must config it and can use the program, els

debconf and program generated config

2005-04-04 Thread Michelle Konzack
Hello, This is the first experience using debconf to configure a bunch of options in a program. The program I am packing generate a config at its first start. Then the admin must config it and can use the program, else it will not start. Now I have created the "templates", "config", "postinst" a