| Summary: | Sort files in do_image_cpio for reproducibility | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ernst Persson <ernstp> | ||||||
| Component: | core | Assignee: | Ross Burton <ross.burton> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher, richard.purdie | ||||||
| Version: | 3.0 | ||||||||
| Target Milestone: | 3.1 | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||||
| Attachments: |
|
||||||||
There's a --reproducible option to cpio also. Perhaps make it optional under BUILD_REPRODUCIBLE_BINARIES ? --reproducible doesn't sort so you'll need to do both. I prefer harmless changes to be done always instead of only in reproducible builds, less combinations for testing. Patches go to the mailing list not bugzilla, so can you please post using git-send-email to openembedded-core@lists.openembedded.org? > --reproducible doesn't sort so you'll need to do both. Yes I meant in addition to. > I prefer harmless changes to be done always instead of only in reproducible builds, less combinations for testing. Sounds good. > Patches go to the mailing list not bugzilla, so can you please post using git-send-email to openembedded-core@lists.openembedded.org? right, of course. Created attachment 4593 [details]
Patch v2
|
Created attachment 4586 [details] Patch Find list files in the order that the filesystem has registered them which can vary. Adding a sort should have minimal performance impact. This should be done in meta/classes/image_types.bbclass