This one time, at band camp, Christian Hamar wrote:
>Hey. Whats output you want to see in new fileconclits check? :)
>
>There are some. (btw sorry, but i dont see how this comes out in a
>mailadress :)
>so little tip, every line is in one line (so if you see that 100% is in
>another newline, then it just a mail bug. Ah the placement is right
>story. At now every progressbar fits size and at same size, just mail
>bug)
>
>First Version:
>---------------
>Proceed with upgrade? [Y/n] y
>
>checking package integrity... done.
>checking for file conflicts: (3/3)        [#######################] 100%
>(1/3) upgrading aspell6-de             [#######################] 100%
>(2/3) upgrading aspell6-hu             [#######################] 100%
>(3/3) upgrading aspell6-vi             [#######################] 100%
>
>Comments: Simple, not writing package name into conflicts files.
>
>
>Second version:
>----------------
>Proceed with upgrade? [Y/n] y
>
>checking package integrity... done.
>checking for file conflicts: (3/3) aspell6-vi [#######################] 100%
>(1/3) upgrading aspell6-de             [#######################] 100%
>(2/3) upgrading aspell6-hu             [#######################] 100%
>(3/3) upgrading aspell6-vi             [#######################] 100%
>
>Comments: There you see package name after counter. This is updated
>every time when pacman checks fileconflicts for another package (no not
>puts into newline or not puts another package name after old package
>name, it just overwrites the old package name with actual one.) so you
>can see what package is beign checked for conflicts at this time.

Is this hard to implement:
Proceed with upgrade? [Y/n] y

checking package integrity... done.
checking for file conflicts:
(3/3) aspell6-vi             [#######################] 100%
installing:
(1/3) upgrading aspell6-de             [#######################] 100%
(2/3) upgrading aspell6-hu             [#######################] 100%
(3/3) upgrading aspell6-vi             [#######################] 100%

Comments: quiet same as the 2nd version, but i think more readable (the line
below "checking for file conflicts:" works as the 2nd version (the line is
updated, only one line).

If this is not OK, then i vote for 2


IroNiQ
-- 
Member of Frugalware Developer Team
Web: http://www.ironiq.hu
LinuxCounter: #331532

Attachment: pgpfzvFLHRP0I.pgp
Description: PGP signature

_______________________________________________
Frugalware-devel mailing list
[email protected]
http://frugalware.org/mailman/listinfo/frugalware-devel

Reply via email to