On Thu, 2008-09-11 at 15:26 -0700, Russ Allbery wrote: > Mark Brown <broonie@sirena.org.uk> writes: > > On Thu, Sep 11, 2008 at 07:21:30PM +0200, Josselin Mouette wrote: > > > The prompts about configuration files could probably be handled by > > having something like a new /usr/share/bug file listing configuration > > that may be desirable. The frontend can then do something sensible with > > the information, at the very least collapsing multiple prompts into a > > single warning. > > Yes -- how much of the interactivity would be taken care of by just having > some way for bug scripts to indicate that the user should be asked "may I > include the following files from your system in the bug report?" and the > results exported in an environment variable or something? debug logs or other files may get too long for a variable but a temporary file would do the job. That's enough interactivity for my scripts, anyway. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
signature.asc
Description: This is a digitally signed message part