[Yum-devel] [PATCH] report total download size

[Michael Favia]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

seth vidal wrote:
> that seems fair - a cleaner layout of the transaction confirmation info
> and possibly the post-transaction result output would be nice.

Oh yeah. i would love to help clean up the post transaction output as well.

> Remember the repository names can be long, too. You might look at what
> yum does for listing package info for available packages via 'yum list'

I did and i tried to find the longest package/repo names i could through
this as well. (system-config-securitylevel-debuginfo seemed to be on the
short list).

I tend to work iteratively instead of proposing wholesale changes for
review and acceptance. As a result i have a few questions and a couple
of suggestions that i would like to put up for discussion before
sugegesting a comprehensive solution.

"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)?

I would also like to provide information to the user on both the
individual package (size, version, etc...) and transation level (disk
space required, ETA, etc) if it can be done concisely and without
overloading. I have made a list of <stress>possible</stress> useful
information for these two areas on the wiki link posted below.

I have begun to reformat my original posting of useful information for
transaction approval but i havent yet had the time to format and display
transaction level information.

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).

Thanks for the comments and suggestions please see the link below for
more information:

http://michael.insitesinc.com/mediawiki/index.php?title=Yum

- --
Michael Favia            michael.favia at insitesinc.com
Insites Incorporated    http://michael.insitesinc.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFB9X46BVsNYjF2rDYRAt65AJ9YoZTNOUFNUz910+M5bQa+awfe0ACcCoYr
ZbxhCfmT4JgedaowYd6K0w4=
=C0+U
-----END PGP SIGNATURE-----