Re: Ideas for `bug'.

[Andreas Jellinghaus <aj@dungeon.inka.de>]

On May 13, Nicolás Lichtmaier wrote
> On Mon, 12 May 1997, Andreas Jellinghaus wrote:
> 
> > no. bug should prompt the user with a list of conffiles before the
> > editor is called. then the user will select the config files to be
> > included, and leater in the editor he can edit them (like replaceing
> > passwords with SECRET and such stuff).
> 
>  What about a `dialog' interface? =)

i didn't try, but it could work :

PARAM=""

for A in `cat /var/lib/dpkg/info/$PACKAGE.conffiles`; do
	PARAM="$PARAM `basename $A` $A 0"
done

dialog --checklist "Include Config Files into Bug Report" 0 0 10 \
	$PARAM 2> /tmp/bug.dialog.$$

if [ -s "`cat /tmp/bug.dialog.$$`" ]; then
	for A in `cat /tmp/bug.dialog.$$`; do
		echo "------ $A"
		cat $A
	done >> /tmp/bug.report.$$;
fi

rm /tmp/bug.dialog.$$

of course a better description would be great. maybe individual packages
can come with there own dialog script like

dialog --checklist "Bug Report about makedev $VERSION" 0 0 10 \
	/etc/devinfo "Database with device descriptions" 1 \
	/etc/makedev.cfg "Database with permissions for various devices" 1 \
	/dev "List of all devices in your /dev (ls -alr /dev)" 1 \
	2>/tmp/bug.makedev.$$

...


regards, andreas


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .