bytes, kilobytes ...

dp · 2003-10-15 10:49:27

this is nothing of importance ... only a eye-candy if corrected, but still something that is worth mentioning

in pacman-output, it looks like this:

[root@Asteraceae damir]# pacman -Suy
:: Synchronizing package databases...
 current.db.tar.gz        [#############################################################] 100% |     33K
 unofficial.db.tar.gz     [#############################################################] 100% |     69K
 unstable.db.tar.gz       [#############################################################] 100% |      0K
 myrepository.db.tar.gz   [/building/DONE/myrepository/                                 ] 100% |   LOCAL

:: ed2k-gtk-gui-0.6.0-1: local version is newer
:: ffmpeg-20030905-1: local version is newer
:: hotplug-2003_08_05-1: local version is newer
:: Above packages will be skipped.  To manually upgrade use 'pacman -S <pkg>'

well, if you look at the unstable.db.tar.gz, you can see it is 0K large ... and if you update e.g. mozilla, than you have thousands of KB --- it would look a little bit nicer, to use bytes if something is less than 1K and M if something is more than 1024K

what about a "human readable" output, like the one you get when you run du or df with the -h?[/b]

sarah31 · 2003-10-15 15:33:58

those tar.gz files mentioned hold skeleton information of the packages within each repository. with only two or three packages in unstable only a few bytes of information are contained within the .tar.gz. thus the reason for the zero K there are way more packages in unofficial than both unstable and official thus more skeleton info thus a larger .tar.gz.

so the readout you get is far more human readable than say bytes which would have to be the setting in order to get a reading on unstable and its skeleton info on three packages.

Arch Linux

#1 2003-10-15 10:49:27

bytes, kilobytes ...

#2 2003-10-15 15:33:58

Re: bytes, kilobytes ...

Board footer