Bug 269 - sstate manifests need to be ordered
Summary: sstate manifests need to be ordered
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 0.9
Hardware: x86 Multiple
: Medium normal
Target Milestone: 0.9 M4
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-09-03 16:07 UTC by Jeff Polk
Modified: 2010-12-21 06:09 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Polk 2010-09-03 16:07:46 UTC
sstate_clean reads the manifest and expects to be able to rmdir directories so the directories need to follow the files in the list
Comment 1 Joshua Lock - Disabled 2010-09-29 03:57:48 UTC
The directories do follow files, but are listed in parent child order. Fixing this could be as simple as calling reverse() on the list of directories...
Comment 2 Richard Purdie 2010-09-29 04:42:48 UTC
I think I'd be happier if the order was explicit.
Comment 3 Joshua Lock - Disabled 2010-09-29 05:09:08 UTC
(In reply to comment #2)
> I think I'd be happier if the order was explicit.

Well, it is in that the list of directories is generated whilst walking the directory tree depth first from the root.

However I can implement this such that the list is first explicitly sorted by length and then reversed, to ensure that the list children (longer entries) are at the top?
Comment 4 Joshua Lock - Disabled 2010-09-29 09:12:01 UTC
Pushed a fix: 62fe6dc755d83a4d394cb8a3751fc6172715ee37

sstate: list directories in child first order in the manifest file
The directory list in the manifest file needs to be sorted such that child
directories are deleted first. Fortunately as the list is generated by walking