On Fri, Oct 27, 2000 at 07:53:06PM +1100, Brian May wrote:
> >>>>> "John" == John Goerzen <jgoerzen@progenylinux.com> writes:
> IMHO using the dpkg-log helps structure the output of the task, and
> what make it easier to have a more professional looking GUI front end.
>
> eg such a program could have GUI fields for
> - current package
dpkg already knows this, and it can already be determined by looking
for "Unpacking ..." or "Setting up ...".
> - current task for this package, as generated by dpkg-log
Which is exactly what this would be outputting.
> - scroll-able list with STDERR and STDOUT output (eg to catch
> shell scripting errors). This could be disabled if desired.
Which would break with debconf (stdout is either used for the
confmodule protocol or for pretty guis). If we were willing to ignore
debconf, we'd be able to just use stdout for the log messages, and
everything'd be fine and dandy.
> - this list could highlight more important events based on the
> parameters based to dpkg-log.
What events here are so important? Why even bother displaying the ones
that aren't important?
Yeesh.
Cheers,
aj
--
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
``We reject: kings, presidents, and voting.
We believe in: rough consensus and working code.''
-- Dave Clark
Attachment:
pgpiNpx5n83SN.pgp
Description: PGP signature