[Yum-devel] [PATCH] report total download size
skvidal at phy.duke.edu
Tue Jan 25 08:00:26 UTC 2005
> "Architecture" and "Action" seem to break my personal rule of repetative
> output that should be "grouped by" instead of output on every line.
> However i dont know much about multi arch and i was wondering if people
> with other archs have to download and manage packages for multiple archs
> (e.g. x86_64 and i386 with some sort of compatability layer on their chip)?
Don't group based on arch - on action, fine - but not arch.
package name, imo, should be listed with arch so it should be:
name.arch in every situation - it saves us two spaces horizontally b/c
we don't need a column separator
> I would appreciate any feedback on the desirability of including such
> information (transaction level) and concerning my questions above.
> I would also like to know what type of organization patterns people find
> most useful for categorization (Indented, divider, no divider).
> Finally, would you like to always use all 80 columns of output or would
> you like to use fewer where possible by computing the maximum strlen of
> the package info and buffering the output just enough to meet specific
> style guides (e.g. 2 space margins on L and R sides).
i'd almost say as short as 76 chars, for postable output via email.
> Thanks for the comments and suggestions please see the link below for
> more information:
It doesn't look too bad - but don't work too hard on balancing the
truncating of the output.
More information about the Yum-devel