Re: How to detect the active debconf frontend?
Frank Küster wrote: > "Olaf van der Spek" <[EMAIL PROTECTED]> wrote: > > >> The alternative would be to check for $DEBIAN_FRONTEND, and if unset > >> parse "debconf-show debconf", but this doesn't look clean. > > > > Shouldn't a clean solution be done in debconf code and not in your package > > code? > > Yes, #367497 Your proposed workaround breaks when the bug is fixed.. Also, if you see the current debconf TODO: Noninteractive frontend: * Just because it's noninteractive doesn't mean it can't output to the console. I think it should so so, at least for errors (in addition to mailing them). That way if an error is displayed and the package install fails you don't just see it dying, you immediatly see why. So patches accepted for this bug. As to the actual question, debconf, by intention, does not provide programs a way to know what frontend is being used. Encouraging fronted-specific behavior leads to unncessary complexity and bugs. -- see shy jo signature.asc Description: Digital signature
Re: How to detect the active debconf frontend?
"Olaf van der Spek" <[EMAIL PROTECTED]> wrote: >> The alternative would be to check for $DEBIAN_FRONTEND, and if unset >> parse "debconf-show debconf", but this doesn't look clean. > > Shouldn't a clean solution be done in debconf code and not in your package > code? Yes, #367497 Thanks, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX)
Re: How to detect the active debconf frontend?
On 5/16/06, Frank Küster <[EMAIL PROTECTED]> wrote: Hi, how can I find out in postinst which debconf frontend is active? In case some particular command fails in postinst, we cannot proceed, and let it "exit 1". However, to inform the user, we display a debconf error, telling him how to fix their system. But if the frontend is noninteractive, the error message will only be sent by e-mail; and if this happens in a chroot where no mail is configured, there's no chance at all to see that. So what we'd like to do is to check whether the frontend is noninteractive, and additionally output to stderr in that case. Therefore, I'm looking for a way to ask debconf about the frontend - is this possible? The alternative would be to check for $DEBIAN_FRONTEND, and if unset parse "debconf-show debconf", but this doesn't look clean. Shouldn't a clean solution be done in debconf code and not in your package code?
Re: How to detect the active debconf frontend?
Rudolf Weeber <[EMAIL PROTECTED]> wrote: > Hi, > On Tue, May 16, 2006 at 12:47:13PM +0200, Frank Küster wrote: >> Hi, >> >> how can I find out in postinst which debconf frontend is active? > debconf-show debconf > and some filter meight work. You should have read my question to the end: , | Therefore, I'm looking for a way to ask debconf about the frontend - is | this possible? | | The alternative would be to check for $DEBIAN_FRONTEND, and if unset | parse "debconf-show debconf", but this doesn't look clean. ` Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX)
Re: How to detect the active debconf frontend?
Hi, On Tue, May 16, 2006 at 12:47:13PM +0200, Frank Küster wrote: > Hi, > > how can I find out in postinst which debconf frontend is active? debconf-show debconf and some filter meight work. CU, Rudolf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
