You are not logged in.
Hi all.
Forgive the idiotic question, but when I -Syu my system and it displays the installed size on my hard drive, is that *new* space that's being used or are the packages that are being updated being overwritten? In theory that would make it possible to have a neutral or small gain/loss as opposed to the large numbers I frequently see when I update. Hopefully that question made sense.
Thanks for the help; this is a great community.
Czar.
Last edited by Czarcasmo (2011-06-09 03:29:30)
Laptop: Lenovo X1 Carbon, Core i7 2.0Ghz, 8GB RAM, Gnome 3.16
Offline
It's the install size of the new packages and does not take into account of what's being removed. This has been brought up here before with no final solution that I'm aware of. It's a bit tricky to search for, so it's understandable that you didn't find an answer.
Offline
If you look in /var/cache/pacman/pkg/ you will see that packages are not overwritten - this allows you to downgrade a package if necessary...
Offline
If you look in /var/cache/pacman/pkg/ you will see that packages are not overwritten - this allows you to downgrade a package if necessary...
Of course. I was thinking of upgrade/replace and not total disc size.
Offline
Hey guys,
Thank you both for the quick reply. I'm assuming that what is kept in /var/cache/pacman/pkg/ is simply one version back, not an entire version history, yes? That could be real hell on my laptop in six months. ![]()
Thanks,
Czar.
EDIT: Just checked myself on a test machine I have in my lab. It seems to keep...well...everything. I'm assuming there's no easy way to keep this 'clean'?
Last edited by Czarcasmo (2011-06-09 03:27:32)
Laptop: Lenovo X1 Carbon, Core i7 2.0Ghz, 8GB RAM, Gnome 3.16
Offline
Hey guys,
Thank you both for the quick reply. I'm assuming that what is kept in /var/cache/pacman/pkg/ is simply one version back, not an entire version history, yes? That could be real hell on my laptop in six months.
Thanks,
Czar.
No. Arch expects you to manage your own system. There are a couple of pacman flags that can help. Reading pacman's man page is very helpful for understanding the options.
Offline
Read man pacman and look for -Sc and -Scc (cache clean).
# edit: too slow sandman ![]()
# edit: damn, didn't look up (shakes fist at skottish)
Offline
Hey guys,
Thank you both for the quick reply. I'm assuming that what is kept in /var/cache/pacman/pkg/ is simply one version back, not an entire version history, yes? That could be real hell on my laptop in six months.
Thanks,
Czar.EDIT: Just checked myself on a test machine I have in my lab. It seems to keep...well...everything. I'm assuming there's no easy way to keep this 'clean'?
Everything is kept until you do a 'pacman -Sc' or 'pacman -Scc'
Check man pacman for details
Beaten by 4 seconds!
Last edited by sand_man (2011-06-09 03:28:56)
![]()
Offline
Thanks everyone for the quick replies AND (too boolean?) not out-and-out telling me to RTFM.
Cheers,
Czar.
Laptop: Lenovo X1 Carbon, Core i7 2.0Ghz, 8GB RAM, Gnome 3.16
Offline
# edit: damn, didn't look up (shakes fist at skottish)
skottish tosses warm tortilla at fist. Rock-paper-scissors become ingredients for tacos. Czarcasmo eats well today.
Last edited by skottish (2011-06-09 03:44:02)
Offline
jasonwryan wrote:# edit: damn, didn't look up (shakes fist at skottish)
skottish tosses warm tortilla at fist. Rock-paper-scissors become ingredients for tacos. Czarcasmo eats well today.
Tortilla? WTF!? Isn't that some sort of limp taco?
Offline
It's somewhat related to https://bugs.archlinux.org/task/12566
Offline
wrong thread...
Last edited by sand_man (2011-06-09 10:48:12)
![]()
Offline
Hey guys,
Thank you both for the quick reply. I'm assuming that what is kept in /var/cache/pacman/pkg/ is simply one version back, not an entire version history, yes? That could be real hell on my laptop in six months.
Thanks,
Czar.EDIT: Just checked myself on a test machine I have in my lab. It seems to keep...well...everything. I'm assuming there's no easy way to keep this 'clean'?
There's this script --> https://bbs.archlinux.org/viewtopic.php?id=9104 , which let's you have better control over which packages to keep in the cache. I have never tried it myself, so can't say how well it works.
Offline
Or a more recent one: http://aur.archlinux.org/packages.php?ID=41918
Offline
FYI, the next release of pacman will have 'net upgrade size' listed for any sync operation that updates a package:
# pacman -Su
Password:
:: Starting full system upgrade...
warning: make: ignoring package upgrade (3.81-5 => 3.82-3)
warning: qemu: ignoring package upgrade (0.13.0-1 => 0.14.1-1)
resolving dependencies...
looking for inter-conflicts...
Targets (1):
Name Old Version New Version Size
qt 4.7.3-2 4.7.3-3 24.59 MiB
Total Download Size: 24.59 MiB
Total Installed Size: 98.12 MiB
Net Upgrade Size: -6.77 MiB
Proceed with installation? [Y/n] Offline
@falconindy
I've seem http://mailman.archlinux.org/pipermail/ … 13211.html patch, but https://bugs.archlinux.org/task/12566 it's not yet marked as solved. According to the ML post, it should work for upgrade (-U) operations too.
Just to be sure: 'Net Upgrade Size: -6.77 MiB' means the new version has the installed size over 6 MB smaller than the old version and it doesn't take the Download Size into account, right?
Offline