When calculating the package size qsize from app-portage/portage-utils-0.2.1 counts each file as many times as there are hardlinks to it. Reproducible: Always Steps to Reproduce: qsize dev-util/git Actual Results: 425271.590 KB for dev-util/git-1.6.4.4 Expected Results: 39456.403 KB /usr/libexec/git-core/git has 97 hardlinks, which counts as additional 96*4115362 bytes or 385815.19 KB
*** This bug has been marked as a duplicate of bug 301026 ***
Reopening, because I can take bug 301026, but someone else'll have to do this one (different program).
that's kind of annoying to have to track ... qsize maintains no information across file entries, and it will have to cache not only the inode, but the device it is stored on as well.
I don't think I'll be coding this feature in either. Hardlinks maybe should be tagged in the VDB itself but the package mgr if there becomes a need. Till then I'm sorry but it seems nobody is insterested in coding this feature right now. However we probably would not reject any community patches that are written to yeild this functionaly as long as there is no overhead for normal usage.
Can it at least check /var/db/pkg/.../.../SIZE and output both sizes if they don't match?
Please rephrase the question. I'm not sure what you are asking.
In the /var/db/pkg/dev-util/git-1.6.4.4/ there is a file SIZE. I don't know exactly what is there, but it contains a number close the correct size of the installed package (maybe rounded up to account for the partially filled disk clusters). What is this size? Can qsize use it?
