RFC Generating a graph of the size installed by each package
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [RFCv1 0/4] Generating a graph of the size installed by each package
Dear Arnout, Yann, Thomas,
Quoted 17 lines · Arnout Vandecappelle
On 24/06/14 15:05, Luca Ceresoli wrote:
[snip]Quoted 15 lines
Quoted 6 lines
The implementation consists in adding a global instrumentation hook that registers which files are installed by each package. A limitation of the current implementation is that when a file is installed by a package A and then overriden by package B, the mechanism will assume the file was installed by package A. Suggestions to welcome on how to solve this in a reasonably simple way.
It's very well possible that I'm missing something, but I don't get why you need to save the list of all installed files.
Can't you just save the whole rootfs size before and after installation? It can be simply computer by 'du -bs $(TARGET_DIR)', and it's way easier to parse later. It would also take into account the change of size for overwritten files, for free.
Quoted 6 lines
Quoted 2 lines
Of course your approach collects more information, but I don't see these extra info used in the final graph.
The reason is explained a bit further in that cover letter: we only do
stripping and removing of redundant stuff in the finalize step, so calculating the size before that doesn't make much sense.
Aaah, yes, stripping! Of course! I was sure there is a good reason...
I'll try to connect my brain to my fingers next time (or at least read the email properly)...
Thanks for having gently replied instead of simply blaming me (which would have made a lot of sense indeed!).
Signature · 1 line
Luca