Summary: | Disk space recovered/freed after an emerge or unmerge | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Marc 'huz' REYNES <marc.reynes> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | alpeterson, magnade, mholzer, morfic |
Priority: | High | ||
Version: | 2.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marc 'huz' REYNES
2003-02-19 05:00:35 UTC
check is done in bug #8545 so this bug is for statistic to print out etcat -s package gives you the size of an installed package, it needs some time for bigger packages, so I don't think this should be integrated in emerge. have it optional then also part of what it would be scanning for size would be in mem cache how many people really want to run/learn the command etcat? it sounds like... somebody ate a feline... No, emerge -Cp package or emerge -p package should say how big it is / how big it is expected to be We always need it, and it shouldn't take more than 3 or 4 characters at the end of the line anyway. 2.3G or 1.4K or 0.5K 100B 12M This is _IMPORTANT_ my system might have just been screwed by running out of diskspace.. and nobody seems to care about this avoidable problem. No chance to make this work with `emerge -p`. "This is _IMPORTANT_ my system might have just been screwed by running out of diskspace.. and nobody seems to care about this avoidable problem." There isn't any easy way to do this for merging, aside from building all packages, and maintaing a central listing of how large each package is. As for listing how much space is freed by removing a package, I guess, although I personally don't see the need. Closing in the interim, if you want the latter (space freed by an unmerge) reopen the bug; implementing both is a bit of a pita, although the latter is possible (not high on my list of priorities though). |