Thanks for all the input! From this discussion I conclude that in my
package's case there is no call for db_input in postinst, so I just
commented out those calls and lintian/linda are happy :)
Maybe it would be useful to summarise the cases where you are pretty
forced to use db_input calls in pos
Thanks for all the input! From this discussion I conclude that in my
package's case there is no call for db_input in postinst, so I just
commented out those calls and lintian/linda are happy :)
Maybe it would be useful to summarise the cases where you are pretty
forced to use db_input calls in pos
On Fri, Dec 12, 2003 at 10:42:34AM -0800, Josh Lauricha wrote:
> On Fri 12/12/03 10:59, Jamin W. Collins wrote:
> > In this particular case it's a concern about not storing a DB admin
> > password in debconf yet still being able to properly remove a package
> > created DB if the user has requested
On Fri 12/12/03 10:59, Jamin W. Collins wrote:
> In this particular case it's a concern about not storing a DB admin
> password in debconf yet still being able to properly remove a package
> created DB if the user has requested the package do so on purge.
Perhaps a db user created on install with
On Fri, Dec 12, 2003 at 10:42:34AM -0800, Josh Lauricha wrote:
> On Fri 12/12/03 10:59, Jamin W. Collins wrote:
> > In this particular case it's a concern about not storing a DB admin
> > password in debconf yet still being able to properly remove a package
> > created DB if the user has requested
On Fri, Dec 12, 2003 at 10:00:16AM +, Colin Watson wrote:
> On Fri, Dec 12, 2003 at 10:42:10AM +0100, Frank K?ster wrote:
> >
> > I can't find it right now, but isn't it written somewhere that prompting
> > in postinst will be a no-no in future policy releases?
>
> It shouldn't be (I think yo
On Fri 12/12/03 10:59, Jamin W. Collins wrote:
> In this particular case it's a concern about not storing a DB admin
> password in debconf yet still being able to properly remove a package
> created DB if the user has requested the package do so on purge.
Perhaps a db user created on install with
On Fri, Dec 12, 2003 at 10:00:16AM +, Colin Watson wrote:
> On Fri, Dec 12, 2003 at 10:42:10AM +0100, Frank K?ster wrote:
> >
> > I can't find it right now, but isn't it written somewhere that prompting
> > in postinst will be a no-no in future policy releases?
>
> It shouldn't be (I think yo
On Fri, Dec 12, 2003 at 10:42:10AM +0100, Frank Küster wrote:
> "Jamin W. Collins" <[EMAIL PROTECTED]> schrieb:
> > On Thu, Dec 11, 2003 at 11:51:01PM +0100, Jeremy Lain? wrote:
> >> I can see how it is a Bad Thing to prompt the user for input both in
> >> postinst and in config, but the fact still
"Jamin W. Collins" <[EMAIL PROTECTED]> schrieb:
> On Thu, Dec 11, 2003 at 11:51:01PM +0100, Jeremy Lain? wrote:
>>
>> I can see how it is a Bad Thing to prompt the user for input both in
>> postinst and in config, but the fact still stands that it's the way
>> it's done in horde2, and I'm sure the
On Fri, Dec 12, 2003 at 10:42:10AM +0100, Frank Küster wrote:
> "Jamin W. Collins" <[EMAIL PROTECTED]> schrieb:
> > On Thu, Dec 11, 2003 at 11:51:01PM +0100, Jeremy Lain? wrote:
> >> I can see how it is a Bad Thing to prompt the user for input both in
> >> postinst and in config, but the fact still
"Jamin W. Collins" <[EMAIL PROTECTED]> schrieb:
> On Thu, Dec 11, 2003 at 11:51:01PM +0100, Jeremy Lain? wrote:
>>
>> I can see how it is a Bad Thing to prompt the user for input both in
>> postinst and in config, but the fact still stands that it's the way
>> it's done in horde2, and I'm sure the
On Thu, Dec 11, 2003 at 11:51:01PM +0100, Jeremy Lain? wrote:
>
> I can see how it is a Bad Thing to prompt the user for input both in
> postinst and in config, but the fact still stands that it's the way
> it's done in horde2, and I'm sure there must be a good reason for it!
> Any ideas here?
As
On Thu, Dec 11, 2003 at 11:51:01PM +0100, Jeremy Lain? wrote:
>
> I can see how it is a Bad Thing to prompt the user for input both in
> postinst and in config, but the fact still stands that it's the way
> it's done in horde2, and I'm sure there must be a good reason for it!
> Any ideas here?
As
Hi!
I am trying to put the finishing touches on a package of Diogenes, a
web content management system. The package relies on a MySQL database,
and this database is created based on some information provided by the
user through debconf. I am down to one lintian warning :
W: diogenes: postinst-use
Hi!
I am trying to put the finishing touches on a package of Diogenes, a
web content management system. The package relies on a MySQL database,
and this database is created based on some information provided by the
user through debconf. I am down to one lintian warning :
W: diogenes: postinst-use
16 matches
Mail list logo
