[Yum-devel] transaction listing

[Chip Turner]

seth vidal <skvidal at phy.duke.edu> writes:

> new example:
>
> =============================================================================
>  Package                 Arch       Version          Repository        Size
> =============================================================================
> Installing:
>  compat-libf2c-32        i386       3.2.3-47.fc4     development        50 k
>      replacing  libf2c                  i386       3.4.3-18
>  compat-libstdc++-296    i386       2.96-132.fc4     development       174 k
>      replacing  compat-libstdc++        i386       8-3.3.4.2
>  compat-libstdc++-33     i386       3.2.3-47.fc4     development       228 k
>      replacing  compat-libstdc++        i386       8-3.3.4.2
>  cryptsetup-luks         i386       0.993-1          development       414 k
>      replacing  cryptsetup              i386       0.1-4
>
> I'm thinking of adding in an extra linefeed after each 'replacing line'
>
> thoughts?

IMO the columns not lining up makes it harder to read; basically the
columns mean different things if it is a regular line or not.  99.9%
of the time, no one will care about the previous arch or version, I
don't think.  The newline idea is probably good, depending on how it
looks with other non-obsoletes (I think it will be okay since the
sections are pretty clearly delineated).  Maybe something like:

Installing:
 compat-libf2c-32        i386       3.2.3-47.fc4     development        50 k
     replacing libf2-3.4.3-18.i386

 compat-libstdc++-296    i386       2.96-132.fc4     development       174 k
     replacing compat-libstdc++-8-3.3.4.2.i386

 compat-libstdc++-33     i386       3.2.3-47.fc4     development       228 k
     replacing compat-libstdc++=8-3.3.4.2.386

 cryptsetup-luks         i386       0.993-1          development       414 k
     replacing cryptsetup-0.1-4.i386

Is a little better to my eyes.

Chip

-- 
Chip Turner                   cturner at pattern.net