-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 11 Sep 2008 17:09:26 +0100 Neil Williams <[EMAIL PROTECTED]> wrote:
> On Thu, 2008-09-11 at 15:35 +0200, Josselin Mouette wrote: > > Le jeudi 11 septembre 2008 à 14:39 +0200, Luca Bruno a écrit : > > > The proposal: > > > I know it's bad to break compatibility but I also think keeping things > > > with hacks and far from the GUI prospective can become obsolete and > > > non user-friendly. > > > > > > First solution: change the scripts to use a bash function instead of > > > cat <<EOF, like yesno() create a function display() without hacking > > > cat() and keep going using a FIFO to deal with the UI > > I can't speak for others but my scripts use yesno(): > yesno "May I include your sources.list (/etc/apt/sources.list)? " yep > > The frontend could execute their own shell wrapper that implements yesno > and sources the bug script (as reportbug does). The other yesno function > can do whatever is necessary to callback into the frontend, get the user > response and feed it back to the script. > > If the frontend can use yesno(), I think it's perfectly reasonable to > expect all packages using bug scripts to use yesno() and not cat <<EOF. > > > > Second solution: I don't know, I'm asking to you > > > > The second solution is to specify that these scripts should not be > > interactive. I don’t think there is much point in it, and it would > > simplify things a lot. > > We've been here before. Some people might value the opportunity to > refuse permission to include sources lists and other data - any > non-interactive frontend must make it absolutely clear that this data > has been included and it is up to the user to delete it. > > Cannot the other frontends do what reportbug does and implement a bash > function that scripts can call? The terminal can be hidden or run via > internal calls, just as long as it pauses and allows the user to make a > decision. > > I suspect the problem with using debconf will be that debconf a) expects > to be run as root and b) is too specialised in how it wants to store > data (which we don't want to do at this point). However, something that > implements a choice of frontends *without losing functionality* is the > best bet. > The problem comes also with yesno(), because the more sane (as far as I know) way to communicate is FIFO. You call the yesno() function, then it writes to the FIFO and request ui.yes_no() from python. But for cat <<EOF, which actually your script is using too, I had to export -f cat hacked to send lines to the FIFO in a particular way. So there's something like a protocol I've created to deal with the python UI. If scripts could use a function like display() that would solve the problem of "overriding" cat(). Reportbug is ok with text and urwid (which also stops curses and switches to text), but the coming GTK+ interface won't support it. You have to switch to the terminal and see what's happening, or alternatively embed a VTE in the wizard. - -- http://syx.googlecode.com - Smalltalk YX http://lethalman.blogspot.com - Thoughts about computer technologies http://www.ammazzatecitutti.org - Ammazzateci tutti -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkjJRXQACgkQw9Qj+8Kak3Gy4ACgh8JtNMg4Sq1qssrLX/zCPdOS BqQAoIMwV6L733xl7VI9AilNdnaczyZO =+UvB -----END PGP SIGNATURE-----
