``` $ emerge -kp --nodeps gcc These are the packages that would be merged, in order: [ebuild U ] sys-devel/gcc-11.2.1_p20220115:11 [11.2.0:11] USE="(cxx) nptl openmp (pie) sanitize ssp vtv zstd (-ada) (-cet) -custom-cflags -d -debug -doc (-fixed-point) -fortran -go -graphite (-hardened) -jit (-libssp) -lto (-multilib) -nls* -objc -objc++ -objc-gc (-pch*) -pgo -systemtap -test -valgrind -vanilla" 0 KiB Total: 1 package (1 upgrade, 1 binary), Size of downloads: 0 KiB ``` If a package is being installed from a binpkg or the package source has already been downloaded, then it would be helpful to change the output from "Size of downloads" (always '0 KiB') to "Size of source" or "Size of binary package" respectively (both at the end of each per-package line of output and in the summary at the end). This may lead to output such as: ``` Total: 3 packages (3 upgrades, 1 binary), Size of downloads: 0 KiB, Size of source: {x} KiB, Size of binary packages: {y} KiB ``` Reproducible: Always Steps to Reproduce: 1. 'emerge' a package with source already downloaded, or for which a binary package has been pre-built. Actual Results: The only stats I'm given are that there is no data to download - I know nothing about the size of the source to be compiled or the size of the binary package to be deployed. Expected Results: More introspection given, to allow a rough estimation of the potential time to install the new package. Rather than showing only Download size, instead show deployment size: e.g. source size for packages to be built or binary package size for pre-built packages.
