How the directory structure will be presented (a hierarchical tree, imitating a desktop file browser, is one possibility) is TBC. The presentation should include information about each directory / file (such as file size). The complete information set is TBC. For an idea of this feature, check: http://www.yoctoproject.org/webhob/phase3_final_web_prototype/project-build-directorystructure.html
Created attachment 1277 [details] Directory structure information A first version of the information required for the directory structure
All the needed info to reconstruct target image (the list of installed packets and the list of files per packet) are collected and available. Moving the UI bug to David, post 1.5
Created attachment 1528 [details] Design 1.1 Image information
Created attachment 1643 [details] Design 1.1 Image information
Created attachment 1753 [details] Design 1.1 Image information Add how to display packages renamed at packaging time (name != installed_name)
*** Bug 5979 has been marked as a duplicate of this bug. ***
case: https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=949
In directory structure, a directory size doesn't include the size of all file under the directory. So now any directory size always be 4KB. I think that the direcory size should be sum of the size of all files under the directory. What's your opinion?
I think that the reported size of directories is correct. On my ubuntu 12.04 host, note that the size is 4096 and accurately reflects the size required for the directory inode, not a total of the size of the sub-directory. That is the linux standard for ls which this view emulates. Given that, then the size displayed for directories should 1) match the size shown in the database table 2) match the size shown for linux systems for directories using ls -l as shown below: poky_16> ls -l . total 19404 drwxr-xr-x 3 dlerner users 4096 Apr 2 17:34 apr_02_builds -rw-r--r-- 1 dlerner users 168 Apr 3 10:54 s.sql -rw-r--r-- 1 dlerner users 19856384 Apr 2 18:29 toaster.sqlite
I think Dave is right. It also matches the information collected by other tools like build history, and it is important we keep consistency in the information collected across all tools.
Got.Thanks. I understand. Verified in 3e528d3e4bc542ca2f654c54363c56af0fb9f61b.