| Summary: |
Drop DEPLOY_DIR_IMAGE from SSTATE_DUPWHITELIST |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
Richard Purdie <richard.purdie> |
| Component: |
core | Assignee: |
Ross Burton <ross.burton> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Undecided
|
CC: |
meta.mr.watcher, meta.watcher
|
| Version: |
2.2 | |
|
| Target Milestone: |
--- | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
Having DEPLOY_DIR_IMAGE in SSTATE_DUPWHITELIST means file overwriting can be masked out a hidden, confusing users as illustrated on IRC recently. There are only a few cases we have file overwriting in the deploy images directory left in OE-Core with the default settings, we should remove them. In particular there are multilib conflicts between: {lib64-,}systemd-boot:do_deploy {lib64-,}grub-efi:do_deploy {lib64-,}ovmf:do_deploy and if these are fixed we should be able to remove this safely for OE-Core.